Coda Story
by
wednesday studio
from United States
-
0Friendliness
-
0Performance
-
0Usability
-
0PWA
-
0Total
Find out more about the Evaluation
Performance 52/100
Speed Index
-
Speed Index5315.69target < 4500 ms
Speed Index is a page load performance metric that shows you how quickly the contents of a page are visibly populated. The lower the score, the better. Source: Lighthouse - Learn more
Document complete
-
Time22.5seconds
-
Resources43requests
-
Bytes in2.4MB
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
-
Time22.5seconds
-
Resources45requests
-
Bytes in2.4MB
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
- codastory.com
- www.google-analytics.com
- www.googletagmanager.com
- hooks.readefined.com
- content.readefined.com
Bytes downloaded
- codastory.com
- www.googletagmanager.com
- www.google-analytics.com
- hooks.readefined.com
- content.readefined.com
Assets by Mime-Type
Requests
- html
- js
- css
- image
- font
Bytes downloaded
- html
- js
- css
- image
- font
Speed
Load time22456 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. Source: WebPagetest - Learn more
Page load is fast enough on 3G
A fast page load over a 3G network ensures a good mobile user experience. Source: Lighthouse - Learn more
First byte3245 ms
The time from the initial request to the first byte of the response. Source: WebPagetest - Learn more
First Contentful Paint2756.286 ms
First contentful paint marks the time at which the first text/image is painted. Source: Lighthouse - Learn more
First meaningful paint3897.076 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. Source: Lighthouse - Learn more
Estimated Input Latency12 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 (< 50ms), users may perceive your app as laggy. Source: Lighthouse - 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. Source: WebPagetest - Learn more
First CPU Idle3897.08 ms
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. Source: Lighthouse - Learn more
Time to Interactive3897.08 ms
Interactive marks the time at which the page is fully interactive. Source: Lighthouse - Learn more
Page weight
Uses compression (gzip, zopfli, deflate, brotli)Score: 99%
This rule triggers when detecting that compressible resources were served without gzip compression. Source: WebPagetest - Learn more
Uses a CDN for all static assetsScore: 95%
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. The 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. Source: WebPagetest - 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. Source: PageSpeed Insights - Learn more
Leverage browser caching for the following cacheable resources:
| URL |
|---|
| https://www.googletagmanager.com/gtag/js?id=UA-123047716-1 (15 minutes) |
| https://www.googletagmanager.com/gtag/js?id=UA-76469608-1 (15 minutes) |
| https://www.google-analytics.com/analytics.js (2 hours) |
| https://codastory.com/wp-content/themes/codastory/assets/fonts/neuehassunica/NeueHaasUnicaW1G-Medium.woff (4 hours) |
| https://codastory.com/wp-content/themes/codastory/assets/fonts/neuehassunica/NeueHaasUnicaW1G-Regular.woff (4 hours) |
| https://codastory.com/wp-content/themes/codastory/assets/fonts/vesterbro/Vesterbro-Extrabold.woff (4 hours) |
| https://codastory.com/wp-content/themes/codastory/assets/fonts/vesterbro/Vesterbro-Light.woff (4 hours) |
| https://codastory.com/wp-content/themes/codastory/assets/fonts/vesterbro/Vesterbro-Medium.woff (4 hours) |
| https://codastory.com/cdn-cgi/scripts/5c5dd728/cloudflare-static/email-decode.min.js (2 days) |
... |
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. Source: PageSpeed Insights - Learn more
Minify CSS for the following resources to reduce their size by 284B (25% reduction).
| URL |
|---|
| Minifying https://codastory.com/wp-content/themes/codastory/style.css?ver=20180799 could save 284B (25% reduction) after compression. |
... |
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. Source: PageSpeed Insights - Learn more
Minify JavaScript for the following resources to reduce their size by 1KiB (27% reduction).
| URL |
|---|
| Minifying https://codastory.com/wp-content/themes/codastory/js/additional.js?ver=20180706 could save 482B (22% reduction) after compression. |
| Minifying https://codastory.com/wp-content/themes/codastory/js/navigation.js?ver=20180706 could save 435B (34% reduction) after compression. |
| Minifying https://codastory.com/wp-content/themes/codastory/js/skip-link-focus-fix.js?ver=20180706 could save 139B (34% reduction) after compression. |
... |
Avoids an excessive DOM size768 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. Source: Lighthouse - Learn more
-
Total DOM Nodes768target < 1,500 nodes
-
DOM Depth18target < 32
-
Maximum Children56target < 60 nodes
Compressed ImagesPotential savings of 6 KB
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. Source: Lighthouse - Learn more
| Thumbnails | URL | Original | Potential Savings |
|---|---|---|---|
 | https://codastory.com/wp-content/uploads/2019/02/GettyImages-1159558-430x430.jpg | 43 KB | 5 KB (12%) |
... |
|||
Uses Progressive JPEGsScore: 18 %
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. Source: WebPagetest - Learn more
Properly Sized ImagesPotential savings of 518 KB
Serve images that are appropriately-sized to save cellular data and improve load time. Source: Lighthouse - Learn more
Offscreen images
Consider lazy-loading offscreen images to improve page load speed and time to interactive. Source: Lighthouse - 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. Source: PageSpeed Insights - Learn more about JS - Learn more about CSS
Your page has 1 blocking script resources and 6 blocking CSS resources. This causes a delay in rendering your page.
| URL |
|---|
| https://codastory.com/wp-content/themes/codastory/js/jquery.js?ver=20180706 |
| https://codastory.com/wp-content/plugins/gutenberg/build/block-library/style.css?ver=1543418454 |
| https://codastory.com/wp-content/themes/codastory/assets/stylesheets/reset.css?ver=20180706 |
| https://codastory.com/wp-content/themes/codastory/assets/stylesheets/main.css?ver=20180719 |
| https://codastory.com/wp-content/themes/codastory/style.css?ver=20180799 |
| https://hooks.readefined.com/css/rwhooks.css |
| https://hooks.readefined.com/css/rwhooks.css |
... |
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. Source: PageSpeed Insights - Learn more
Avoids landing page redirects1
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. Source: PageSpeed Insights - Learn more
Report created on Feb 18, 2019, 15:12 PM GMT+0 in 15 min.
This report was built manually by Awwwards experts taking care personally of every detail using several Google and 3rd-party 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 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3440.106 Safari/537.36 |
| Device Emulation | Emulated Nexus 5X | |
| Network Throttling | 150ms TCP RTT, 1,638.4 Kbps throughput (Simulated) | |
| CPU Throttling | 4x slowdown (Simulated) | |
| PageSpeed Insights | Environment | Mobile |