AMP Website Builder
by
AMP Website Builder
from United Kingdom
-
0Friendliness
-
0Performance
-
0Usability
-
0PWA
-
0Total
Find out more about the Evaluation
Performance 55/100
Speed Index
-
Speed Index8358target < 4000 ms
The Speed Index measures how quickly the page contents are visually populated / painted, and computes an overall score where lower numbers are better. It is expressed in milliseconds and dependent on size of the viewport (above-the-fold contents). Learn more
Document complete
-
Time11.1seconds
-
Resources36requests
-
Bytes in1.6MB
These metrics are collected from the initial request until the browser considers the page loaded (JavaScript onLoad event). This usually happens after all of the image content has loaded but may not include content that is triggered by javascript execution.
Fully load
-
Time17.4seconds
-
Resources37requests
-
Bytes in1.9MB
These metrics are collected from the initial request until 2 seconds of no network activity after Document Complete (JavaScript onLoad event). This will usually include any activity that is triggered by javascript after the main page loads.
Assets by Domain
Requests
- fonts.gstatic.com
- ampwebsitebuilder.com
- cdn.ampproject.org
- i.ytimg.com
- fonts.googleapis.com
- maxcdn.bootstrapcdn.com
Bytes downloaded
- ampwebsitebuilder.com
- fonts.gstatic.com
- cdn.ampproject.org
- maxcdn.bootstrapcdn.com
- i.ytimg.com
- fonts.googleapis.com
Assets by Mime-Type
Requests
- html
- js
- css
- image
- font
Bytes downloaded
- html
- js
- css
- image
- font
Speed
Load time11145 ms
Also known as the document complete time, it’s the time from the initial request until the browser load event. It can vary based on server location, device, browser, and third-party apps. Learn more
Page load is fast enough on 3G
A fast page load over a 3G network ensures a good mobile user experience. Learn more
First byte1509 ms
The time from the initial request to the first byte of the response. Learn more
First meaningful paint8044 ms
First meaningful paint measures when the primary content of a page is visible. It's essentially the paint after which the biggest above-the-fold layout change has happened, and web fonts have loaded. Learn more
Estimated Input Latency16 ms (target < 50 ms)
The score above is an estimate of how long your app takes to respond to user input, in milliseconds. There is a 90% probability that a user encounters this amount of latency, or less. 10% of the time a user can expect additional latency. If your score is higher than Lighthouse's target score (< 50 ms), users may perceive your app as laggy. Learn more
Uses persistent connections (keep alive)Score: 100%
Closing connections are a missed opportunity for performance enhancement: additional round-trips between the user and the server to initiate a connection is redundant and time-consuming. Keep-Alive measures the effectiveness of connection reuse. The purpose of this grade is to evaluate the extent to which requests are inefficiently reopening connections. Learn more
First interactive (beta - experimental)16611 ms
The first point at which necessary scripts of the page have loaded and the CPU is idle enough to handle most user input (with the possibility of slow responses as more content loads). Learn more
Consistently Interactive (beta - experimental)18147 ms
The point at which most network resources have finished loading and the CPU is idle for a prolonged period. Consistently Interactive requires a minimum of 5 seconds of both main thread idle and network idle. In other words, the point where the page is complete and will respond quickly to user input. Learn more
Page weight
Uses compression (gzip, zopfli, deflate, brotli)Score: 100%
This rule triggers when detecting that compressible resources were served without gzip compression. Learn more
Uses a CDN for all static assetsScore: 100%
Each request for a piece of content to the web server has to travel from the user's browser all the way to the server and back. A content delivery network (CDN) is a system for distributing resources to servers geographically closer to users. Main benefit of this is that the round-trip time is faster. The passing grade for using a CDN effectively is to have at least 80% of static resources served from a CDN. Learn more
Leverage browser caching
Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network. Learn more
Leverage browser caching for the following cacheable resources:
| URL |
|---|
| https://static.doubleclick.net/instream/ad_status.js (15 minutes) |
| https://cdn.ampproject.org/v0.js (50 minutes) |
| https://i.ytimg.com/vi/2Qfuj6reHQ8/sddefault.jpg (2 hours) |
| https://i.ytimg.com/vi/C32W30fn4xA/sddefault.jpg (2 hours) |
| https://i.ytimg.com/vi/lBTCB7yLs8Y/sddefault.jpg (2 hours) |
... |
Minify CSS
Minification refers to the process of removing unnecessary or redundant data in order to reduce file size without affecting how the resource is processed by the browser - e.g. code comments and formatting, removing unused code, using shorter variable and function names, and so on. Learn more
Minify HTML
Minification refers to the process of removing unnecessary or redundant data in order to reduce file size without affecting how the resource is processed by the browser - e.g. code comments and formatting, removing unused code, using shorter variable and function names, and so on. Learn more
Minify JavaScript
Minification refers to the process of removing unnecessary or redundant data in order to reduce file size without affecting how the resource is processed by the browser - e.g. code comments and formatting, removing unused code, using shorter variable and function names, and so on. Learn more
Avoids an excessive DOM size691 nodes
Number of elements in the document. Browser engineers recommend pages contain fewer than ~1,500 DOM nodes. The sweet spot is a tree depth < 32 elements and fewer than 60 children/parent element. A large DOM can increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn more
-
Total DOM Nodes691target < 1,500 nodes
-
DOM Depth11target < 32
-
Maximum Children41target < 60 nodes
Compressed ImagesPotential savings of 183 KB (~950 ms)
The image compression check just looks at photo images and makes sure the quality isn't set too high. Images can usually be compressed pretty substantially without any noticeable reduction in visual quality. Learn more
| Thumbnails | URL | Original | Potential Savings |
|---|---|---|---|
 | https://ampwebsitebuilder.com/assets/images/background4-1.jpg | 199 KB | 173 KB (87%) |
 | https://ampwebsitebuilder.com/assets/images/background7.jpg | 64 KB | 11 KB (17%) |
... |
|||
Uses Progressive JPEGsScore: 0 %
A progressive JPEG is image created using the JPEG suite of compression algorithms that will 'fade in' in successive waves of lines until the entire image has completely arrived. They show the entire image right away, looking slightly pixelated until the image data is fully loaded. Learn more
Properly Sized ImagesPotential savings of 471 KB (~2,440 ms)
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more
Offscreen imagesPotential savings of 1,130 KB (~5,860 ms)
Consider lazy-loading offscreen images to improve page load speed and time to interactive. Learn more
First impression
Eliminates render-blocking JavaScript and CSS in above-the-fold content
This rule triggers when detecting that your HTML references a blocking external resource / file in the above-the-fold portion of your page. Learn more about JS - Learn more about CSS
Your page has 5 blocking CSS resources. This causes a delay in rendering your page.
| URL |
|---|
| https://fonts.googleapis.com/css?family=Raleway:100,100i,200,200i,300,300i,400,400i,500,500i,600,600i,700,700i,800,800i,900,900i |
| https://fonts.googleapis.com/css?family=Raleway:100,100i,200,200i,300,300i,400,400i,500,500i,600,600i,700,700i,800,800i,900,900i |
| https://fonts.googleapis.com/css?family=Poppins:100,100i,200,200i,300,300i,400,400i,500,500i,600,600i,700,700i,800,800i,900,900i |
| https://fonts.googleapis.com/css?family=Muli:200,200i,300,300i,400,400i,600,600i,700,700i,800,800i,900,900i |
| https://fonts.googleapis.com/css?family=Poppins:100,100i,200,200i,300,300i,400,400i,500,500i,600,600i,700,700i,800,800i,900,900i |
... |
Prioritizes visible content
This rule triggers when detecting that additional network round trips are required to render the above-the-fold content of the page. Learn more
Improves server response time
This rule triggers when detecting that your server response time is above 200 ms. Server response time measures how long it takes to load the necessary HTML to begin rendering the page from your server, subtracting out the network latency between Google and your server. Learn more
Avoids landing page redirects
Redirects trigger an additional HTTP request-response cycle and delay page rendering. In the best case, each redirect will add a single round trip (HTTP request-response), and in the worst it may result in multiple additional roundtrips to perform the DNS lookup, TCP handshake, and TLS negotiation in addition to the additional HTTP request-response cycle. As a result, you should minimize use of redirects to improve site performance. Learn more
Report created in 15 min.
This report was built using several Google, 3rd-party and Awwwards audit tools and services for metrics, web performance optimization, and best practices for mobile design and development.
Loading time vary depending on network, device, server, site design, and implementation.
These are the environments used to create this report:
| Webpagetest | Test Location | Dulles VA USA |
| Browser | MotoG4 Chrome | |
| Connection | Mobile 3G (1.6 Mbps / 768 Kbps 300ms RTT) | |
| Number of Runs | 1 | |
| User Agent | Default | |
| Lighthouse | User agent | Mozilla/5.0 (Linux; Android 6.0.1; Nexus 5 Build/MRA58N) AppleWebKit/537.36(KHTML, like Gecko) Chrome/61.0.3116.0 Mobile Safari/537.36 |
| Device Emulation | Nexus 5X o MotoG | |
| Network Throttling | 1.4Mbps down, 0.7Mbps up, 562.5ms RTT (PageSpeed uses Chrome on Moto G4 within a 3G network) | |
| CPU Throttling | 4x slowdown | |
| PageSpeed Insights Mobile | Environment | Default |
| TestMySite | Environment | Default |