From d5368e5f90efa026b6ab4c77130aa6ce636c2560 Mon Sep 17 00:00:00 2001 From: Loic Kartono Date: Tue, 3 Feb 2015 10:51:48 +1100 Subject: [PATCH] Chore : Fix typo on policies --- lib/metadata/policies.js | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/lib/metadata/policies.js b/lib/metadata/policies.js index b2b70fd..6051996 100644 --- a/lib/metadata/policies.js +++ b/lib/metadata/policies.js @@ -186,7 +186,7 @@ var policies = { "cssRules": { "tool": "phantomas", "label": "Rules count", - "message": "

Having a huge number of CSS rules hurts performances. If the number of CSS rules is higher than the number of DOM elements, there is clearly a problem.

Huge stylesheets generally occur when the different pages of a website load all the CSS, concatenated in a single stylesheet, even if a large part of the rules are page-specific. Solution is to create one main CSS file with global rules and one custom files per page.

", + "message": "

Having a huge number of CSS rules hurts performances. If the number of CSS rules is higher than the number of DOM elements, there is clearly a problem.

Huge stylesheets generally occur when the different pages of a website load all the CSS, concatenated in a single stylesheet, even if a large part of the rules are page-specific. Solution is to create one main CSS file with global rules and one custom file per page.

", "isOkThreshold": 500, "isBadThreshold": 2500, "isAbnormalThreshold": 4000 @@ -395,7 +395,7 @@ var policies = { "notFound": { "tool": "phantomas", "label": "404 not found", - "message": "

404 errors are never cached, so each time a page ask for it, it hits se server. Even if it is behind a CDN or a reverse-proxy cache.

", + "message": "

404 errors are never cached, so each time a page ask for it, it hits the server. Even if it is behind a CDN or a reverse-proxy cache.

", "isOkThreshold": 0, "isBadThreshold": 1, "isAbnormalThreshold": 1 @@ -403,7 +403,7 @@ var policies = { "closedConnections": { "tool": "phantomas", "label": "Connections closed", - "message": "

This counts the number of requests not keeping the connection alive (specifying \"Connection: close\" in the response headers). It is only counting a request if it is followed by another request on the same domain.

This is slowing down the next request, because the brower needs to open a new connection to the server, which means a additional round-trip.

Correct the problem by setting a Keep-Alive header on the guilty server.

", + "message": "

This counts the number of requests not keeping the connection alive (specifying \"Connection: close\" in the response headers). It is only counting a request if it is followed by another request on the same domain.

This is slowing down the next request, because the brower needs to open a new connection to the server, which means an additional round-trip.

Correct the problem by setting a Keep-Alive header on the guilty server.

", "isOkThreshold": 0, "isBadThreshold": 8, "isAbnormalThreshold": 20