Professional Documents
Culture Documents
Executive Summary
PageSpeed Score YSlow Score Fully Loaded Time Total Page Size Requests
https://carbon60.com/
Nectar for Whats - Prospect mais clientes pelo WhatsApp | Nectar CRM
nectar-for-whats 200 nectarcrm.com.br 41.8KB 855ms
n-icon-logo-nectar-for-whats-1.svg 200 scdn.nectarcrm.com.br 1.30KB 39ms
jquery.min.js?ver=02dd5d04add4 200 nectarcrm.com.br 30.2KB 176ms
jquery-migrate.min.js?ver=79b4956b7… 200 nectarcrm.com.br 4.07KB 170ms
f5ff9cfb41da.page-822.used.css 200 nectarcrm.com.br 18.9KB 316ms
new-tab.js?ver=a1ade95e2110 200 nectarcrm.com.br 8.61KB 192ms
avia-footer-scripts-4d529343bf501c8b… 200 nectarcrm.com.br 54.4KB 331ms
Banner-1-2-1.png 200 scdn.nectarcrm.com.br 78.5KB 3ms
circularstd-black.woff 200 nectarcrm.com.br 38.2KB 283ms
icomoon.woff2 200 nectarcrm.com.br 7.52KB 338ms
circularstd-bold.woff 200 nectarcrm.com.br 38.4KB 333ms
inter-medium.ttf 200 nectarcrm.com.br 154KB 638ms
inter-regular.ttf 200 nectarcrm.com.br 145KB 615ms
entypo-fontello.woff2 200 nectarcrm.com.br 38.3KB 340ms
inter-semibold.ttf 200 nectarcrm.com.br 155KB 612ms
logo_nectar_grey.svg 200 scdn.nectarcrm.com.br 2.46KB 3ms
Frame-409-1030x594.png 200 scdn.nectarcrm.com.br 46.9KB 3ms
circularstd-regular.woff 200 nectarcrm.com.br 33.9KB 531ms
?h=786d678a5703ff4a9834f.551fec7c… 200 forms.pipz.io 9.22KB 1.4s
Frame-1358-1030x630.png 200 scdn.nectarcrm.com.br 20.5KB 8ms
Frame-1359-1030x630.png 200 scdn.nectarcrm.com.br 16.5KB 10ms
Frame-1361-1030x630.png 200 scdn.nectarcrm.com.br 14.7KB 9ms
Frame-1360-1030x630.png 200 scdn.nectarcrm.com.br 22.4KB 10ms
BG.png 200 scdn.nectarcrm.com.br 33.1KB 6ms
inter-bold.ttf 200 nectarcrm.com.br 156KB 300ms
favicon-128x128-1-80x80.png 200 scdn.nectarcrm.com.br 2.64KB 3ms
imask.min.js 200 cdnjs.cloudflare.com 13.3KB 25ms
moment.min.js 200 cdnjs.cloudflare.com 15.1KB 26ms
28 Requests 1.17MB (2.35MB Uncompressed) Fully Loaded 2.5s (Onload 1.6s)
0ms 358ms
Redirect Connect
331ms 689ms
Backend TTFB
898ms 976ms
First Paint Contentful Paint
1.0s 1.2s (0ms)
DOM Int. DOM Loaded
1.6s (4ms)
Onload
Redirect Duration
This is the time spent redirecting URLs before the final HTML page is loaded. Common redirects include:
Redirect from a non-www to www (eg. example.com to www.example.com)
Redirect to a secure URL (eg. http:// to https://)
Redirect to set cookies
Redirect to a mobile version of the site
Some sites may even perform a chain of multiple redirects (eg. non-www to www, then to a secure URL). This
timing is the total of all this time that's spent redirecting, or 0 if no redirects occurred.
In the Waterfall Chart, Redirect duration consists of the time from the beginning of the test until just before we start the request of the final HTML page
(when we receive the first 200 OK response).
During this time, the browser screen is blank! Ensure that this duration is kept to short by minimizing your redirects.
Connection Duration
Once any redirects have completed, Connection duration is measured. This is the time spent connecting to the
server to make the request to the page.
Technically speaking, this duration is a combination of the blocked time, DNS time, connect time and sending
time of the request (rather than just connect time). We've combined those components into a single Connection
duration to simplify things (as most of these times are usually small).
In the Waterfall Chart, Connection duration consists of everything up to and including the "Sending" time in the
final HTML page request (the first 200 OK response).
During this time, the browser screen is still blank! Various causes could contribute to this, including a slow/problematic connection between the test server
and site or slow response times from the site.
Backend Duration
Once the connection is complete and the request is made, the server needs to generate a response for the
page. The time it takes to generate the response is known as the Backend duration.
In the Waterfall Chart, Backend duration consists of purple waiting time in the page request.
There are a number of reasons why Backend duration could be slow. We cover this is our "Why is my page
slow" article.
First Paint
First paint time is the first point at which the browser does any sort of rendering on the page. Depending on the
structure of the page, this first paint could just be displaying the background colour (including white), or it could
be a majority of the page being rendered.
In the Waterfall Chart, it is represented by the green line.
This timing is of significance because until this point, the browser will have only shown a blank page and this
change gives the user an indication that the page is loading. However, we don't know how much of the page
was rendered with this paint, so having a early first paint doesn't necessarily indicate a fast loading page.
If the browser does not perform a paint (ie. the html results in an blank page), then the paint timings may be missing.
If the browser does not perform a paint (ie. the html results in an blank page), then the paint timings may be missing.
Onload Time
Onload time occurs when the processing of the page is complete and all the resources on the page (images,
CSS, etc.) have finished downloading. This is also the same time that DOM complete occurs and the
JavaScript window.onload event fires.
Note that there may be JavaScript that initiates subsequent requests for more resources, hence the reason why
Fully loaded timing is preferred.
In the Waterfall Chart, it is represented by the red line.
The time in brackets is the time spent executing JavaScript triggered by the Onload event.
Note that Onload time was the previous default for when to stop the test prior to Feburary 8th, 2017.
Avoid a character set in the meta tag A (100) AVG SCORE: 100%
Avoid HTTP 404 (Not Found) error A (100) AVG SCORE: 99%