Mobile Excellence / Fishing the Feed
Nov 07, 2019, 15:30

Fishing the Feed

by Fiasco Design from United Kingdom
  • 0
    Friendliness
  • 0
    Performance
  • 0
    Usability
  • 0
    PWA
  • 0
    Total
Find out more about the Evaluation

Mobile Friendliness 100/100

Configures the viewport

This rule triggers when detecting that your page does not specify a viewport, or specifies a viewport that does not adapt to different devices. Source: PageSpeed Insights - Learn more

Content is sized correctly for the viewport

If the width of your app's content doesn't match the width of the viewport, your app might not be optimized for mobile screens. Source: Lighthouse - Learn more

Size tap targets appropriately

This rule triggers when detecting that certain tap targets (e.g. buttons, links, or form fields) may be too small or too close together for a user to easily tap on a touchscreen. Source: PageSpeed Insights - Learn more

Uses legible font sizes

This rule triggers when detecting that text in the page is too small to be legible. Source: PageSpeed Insights - Learn more

Color Contrast is satisfactory

Low-contrast text is difficult or impossible for many users to read. Background and foreground colors should have enough contrast ratio to guarantee readability. Source: Lighthouse - Learn more

Performance 63/100

Speed Index

  • Speed Index
    6897.39
    target < 4500 ms

Perceptual 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

  • Time
    108.2
    seconds
  • Resources
    68
    requests
  • Bytes in
    16
    MB

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

  • Time
    110.5
    seconds
  • Resources
    69
    requests
  • Bytes in
    16
    MB

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

  • j3a3p9y4.stackpathcdn.com

  • www.youtube.com

  • platform.twitter.com

  • www.google-analytics.com

  • fonts.gstatic.com

  • www.fishingthefeed.com

  • www.google.com

  • i.ytimg.com

  • s.ytimg.com

  • www.googletagmanager.com

  • syndication.twitter.com

  • yt3.ggpht.com

  • static.doubleclick.net

Bytes downloaded

  • j3a3p9y4.stackpathcdn.com

  • www.youtube.com

  • i.ytimg.com

  • s.ytimg.com

  • platform.twitter.com

  • www.googletagmanager.com

  • www.google-analytics.com

  • fonts.gstatic.com

  • www.fishingthefeed.com

  • www.google.com

  • yt3.ggpht.com

  • syndication.twitter.com

  • static.doubleclick.net

Assets by Mime-Type

Requests

  • html

  • js

  • css

  • image

  • font

  • video

  • other

Bytes downloaded

  • html

  • js

  • css

  • image

  • font

  • video

  • other

Speed

Load time108220 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 byte1743 ms

The time from the initial request to the first byte of the response. Source: WebPagetest - Learn more

First Contentful Paint3290.9945 ms

First contentful paint marks the time at which the first text/image is painted. Source: Lighthouse - Learn more

First meaningful paint4482.377 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 Idle4482.38 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 Interactive4482.38 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: 52%

This rule triggers when detecting that compressible resources were served without gzip compression. Source: WebPagetest - Learn more

Uses a CDN for all static assetsScore: 98%

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://static.doubleclick.net/instream/ad_status.js (15 minutes)
https://www.googletagmanager.com/gtag/js?id=UA-145607346-2 (15 minutes)
https://platform.twitter.com/widgets.js?ver=1.3 (30 minutes)
https://j3a3p9y4.stackpathcdn.com/wp-content/cache/minify/38919.js (60 minutes)
https://j3a3p9y4.stackpathcdn.com/wp-content/cache/minify/3fd89.js (60 minutes)
https://j3a3p9y4.stackpathcdn.com/wp-content/cache/minify/fb8bc.css (60 minutes)
https://www.google-analytics.com/analytics.js (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. Source: PageSpeed Insights - 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. Source: PageSpeed Insights - 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. Source: PageSpeed Insights - Learn more

Avoids an excessive DOM size1072 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 Nodes
    1,072
    target < 1,500 nodes
  • DOM Depth
    11
    target < 32
  • Maximum Children
    43
    target < 60 nodes

Compressed ImagesPotential savings of 562 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

ThumbnailsURLOriginalPotential Savings
https://j3a3p9y4.stackpathcdn.com/wp-content/themes/changing-markets/img/Mobile/Scene04.jpg546 KB99 KB (18%)
https://j3a3p9y4.stackpathcdn.com/wp-content/themes/changing-markets/img/Mobile/Scene03.jpg421 KB83 KB (19%)
https://j3a3p9y4.stackpathcdn.com/wp-content/themes/changing-markets/img/Mobile/Scene02.jpg382 KB75 KB (19%)
https://j3a3p9y4.stackpathcdn.com/wp-content/themes/changing-markets/img/Mobile/Scene05.jpg326 KB69 KB (21%)
https://j3a3p9y4.stackpathcdn.com/wp-content/themes/changing-markets/img/Mobile/Scene08.jpg359 KB56 KB (15%)
https://j3a3p9y4.stackpathcdn.com/wp-content/themes/changing-markets/img/Mobile/Scene07.jpg238 KB48 KB (20%)
https://j3a3p9y4.stackpathcdn.com/wp-content/themes/changing-markets/img/Mobile/Scene09.jpg279 KB44 KB (16%)
https://j3a3p9y4.stackpathcdn.com/wp-content/themes/changing-markets/img/Mobile/Scene01.jpg155 KB38 KB (24%)
https://j3a3p9y4.stackpathcdn.com/wp-content/themes/changing-markets/img/Mobile/Scene06.jpg187 KB35 KB (19%)
https://j3a3p9y4.stackpathcdn.com/wp-content/themes/changing-markets/img/watercolour-1.jpg50 KB9 KB (19%)
...

Uses Progressive JPEGsScore: 42 %

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 667 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 1 blocking CSS resources. This causes a delay in rendering your page.

URL
https://j3a3p9y4.stackpathcdn.com/wp-content/cache/minify/38919.js
https://j3a3p9y4.stackpathcdn.com/wp-content/cache/minify/fb8bc.css
...

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. Source: PageSpeed Insights - 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. Source: PageSpeed Insights - 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. Source: PageSpeed Insights - Learn more

Usability 75/100 Industry: Lead Gen

Key and appropriate information is provided and is easy to find on the product page e.g. APR, key benefits, etc

Fails if information is missing or hard to find.

Relevant product/service details are concise and use bullet points to make it easy for the user to skim and scan the content for understanding

Fails if content is laid out in text form and large paragraphs requiring the user to seek out the information themselves by reading large bodies of text.

Phone numbers are clickable to make callsNot applicable

Fails if missing tap to call functionality.

Links never open new browser tabs unless clearly indicated or users can back arrow to the previous page

Fails if opening new browser tabs without warning the user in advance that this will happen.

Access to instant, responsive support (web chat or phone) within office hours is available at any point

Fails if missing or hard to find contact options. Contact options should align with regional expectations.

Optional fields are clearly optionalNot applicable

Fails if it is not clear that optional fields are optional, i.e. They do not say 'optional' or they do not follow the pattern of no asterisk for optional, while compulsory fields do.

The most appropriate keyboard for the input type is provided firstNot applicable

Fails if most helpful keyboard not provided, i.e. input types text, tel, email, password, capitalization when appropiate, etc.

The website supports autofill for all form fields and the fields are tagged for the appropriate information from autofillNot applicable

Fails if fields are not tagged for efficient browser-based autofill, making users enter data that is already known either by the website or the OS. Not filling a standard field or filling fields with the wrong content, i.e. puts house number and street name into the same field when there are separate fields for each.

All mistakes made in forms are clearly highlighted in real time, and instructions for correct completion are provided in real timeNot applicable

Fails if mistakes and guidance for correct completion are not highlighted in real time and/or error messages are ambiguous or unfriendly.

Within a form, users can navigate back and forth between steps/pages without losing previously inputted informationNot applicable

Fails if a user backtracks and previously entered data is lost.

PWA / Best Practices 82/100

Avoids Application Cache

Application Cache is deprecated. Source: Lighthouse - Learn more

Avoids WebSQL DB

Web SQL is deprecated. Consider using IndexedDB instead. Source: Lighthouse - Learn more

Avoids requesting the geolocation permission on page load

Users are mistrustful of or confused by sites that request their location without context. Consider tying the request to user gestures instead. Source: Lighthouse - Learn more

robots.txt is valid

If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Source: Lighthouse

Avoids requesting the notification permission on page load

Users are mistrustful of or confused by sites that request to send notifications without context. Consider tying the request to user gestures instead. Source: Lighthouse - Learn more

Avoids deprecated APIs

Deprecated APIs will eventually be removed from the browser. Source: Lighthouse - Learn more

Allows to paste into password input fields

The main reason why password pasting improves security is because it helps to reduce password overload. Source: Lighthouse - Learn more

Registers a Service Worker

The service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. Source: Lighthouse - Learn more

Responds with a 200 when offline

If you're building a Progressive Web App, consider using a service worker so that your app can work offline. Source: Lighthouse - Learn more

Uses HTTPS

All sites should be protected with HTTPS, even ones that don't handle sensitive data. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Source: Lighthouse - Learn more

Redirects HTTP traffic to HTTPS

If you've already set up HTTPS, make sure that you redirect all HTTP traffic to HTTPS. Source: Lighthouse - Learn more

Uses HTTP/2 for its own resources1 request not served via HTTP/2

HTTP/2 offers many benefits over HTTP/1.1, including binary headers, multiplexing, and server push. Source: Lighthouse - Learn more

Uses passive listeners to improve scrolling performance

Mark your touch and wheel event listeners as `passive` to improve your page's scroll performance. Source: Lighthouse - Learn more

Avoid using document.write()

For users on slow connections, external scripts dynamically injected via document.write() can delay page load by tens of seconds. Source: Lighthouse - Learn more

Manifest's short_name won't be truncated when displayed on homescreen

Make your app's short_name fewer than 12 characters to ensure that it's not truncated on homescreens. Source: Lighthouse - Learn more

Configured for a custom splash screen

A default splash screen will be constructed for your app, but satisfying these requirements guarantee a high-quality splash screen that transitions the user from tapping the home screen icon to your app's first paint. Source: Lighthouse - Learn more

User can be prompted to Install the Web App

Browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement. Source: Lighthouse - Learn more

Mobile Friendliness 80/100

Configures the viewport

This rule triggers when detecting that your page does not specify a viewport, or specifies a viewport that does not adapt to different devices. Source: PageSpeed Insights - Learn more

Content is sized correctly for the viewport

If the width of your app's content doesn't match the width of the viewport, your app might not be optimized for mobile screens. Source: Lighthouse - Learn more

Size tap targets appropriately

This rule triggers when detecting that certain tap targets (e.g. buttons, links, or form fields) may be too small or too close together for a user to easily tap on a touchscreen. Source: PageSpeed Insights - Learn more

Uses legible font sizes

This rule triggers when detecting that text in the page is too small to be legible. Source: PageSpeed Insights - Learn more

Color Contrast is satisfactory

Low-contrast text is difficult or impossible for many users to read. Background and foreground colors should have enough contrast ratio to guarantee readability. Source: Lighthouse - Learn more

Failing Elements

ImpactSnippetTargetFailure Summary
serious<p>Fishing the Feed is a project by the Changing Markets Foundation in partnership with...</p>.footer-middle > pFix any of the following: Element has insufficient color contrast of 2.58 (foreground color: #58515e, background color: #110619, font size: 9.8pt, font weight: normal). Expected contrast ratio of 4.5:1
serious<p>© Changing Markets Foundation 2019<br> Designed and built by <a href="https://fiasco.design" title="Fiasco Design Website">Fiasco Design</a></p>.footer-bottom > pFix any of the following: Element has insufficient color contrast of 2.58 (foreground color: #58515e, background color: #110619, font size: 9.8pt, font weight: normal). Expected contrast ratio of 4.5:1
...

Performance 70/100

Speed Index

  • Speed Index
    4598.23
    target < 4500 ms

Perceptual 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

  • Time
    19.3
    seconds
  • Resources
    36
    requests
  • Bytes in
    1.9
    MB

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

  • Time
    20.1
    seconds
  • Resources
    37
    requests
  • Bytes in
    1.9
    MB

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

  • j3a3p9y4.stackpathcdn.com

  • www.fishingthefeed.com

  • platform.twitter.com

  • www.google-analytics.com

  • www.googletagmanager.com

  • syndication.twitter.com

Bytes downloaded

  • j3a3p9y4.stackpathcdn.com

  • platform.twitter.com

  • www.googletagmanager.com

  • www.google-analytics.com

  • www.fishingthefeed.com

  • syndication.twitter.com

Assets by Mime-Type

Requests

  • html

  • js

  • css

  • image

  • font

  • other

Bytes downloaded

  • html

  • js

  • css

  • image

  • font

  • other

Speed

Load time19327 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 byte3041 ms

The time from the initial request to the first byte of the response. Source: WebPagetest - Learn more

First Contentful Paint3174.248 ms

First contentful paint marks the time at which the first text/image is painted. Source: Lighthouse - Learn more

First meaningful paint4141.874 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 Idle4141.87 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 Interactive4141.87 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: 100%

This rule triggers when detecting that compressible resources were served without gzip compression. Source: WebPagetest - 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. 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://syndication.twitter.com/settings (10 minutes)
https://www.googletagmanager.com/gtag/js?id=UA-145607346-2 (15 minutes)
https://platform.twitter.com/widgets.js?ver=1.3 (30 minutes)
https://j3a3p9y4.stackpathcdn.com/wp-content/cache/minify/383e9.js (60 minutes)
https://j3a3p9y4.stackpathcdn.com/wp-content/cache/minify/3fd89.js (60 minutes)
https://j3a3p9y4.stackpathcdn.com/wp-content/cache/minify/86a1a.css (60 minutes)
https://www.google-analytics.com/analytics.js (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. Source: PageSpeed Insights - 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. Source: PageSpeed Insights - Learn more

Minify HTML for the following resources to reduce their size by 467B (12% reduction).

URL
Minifying https://www.fishingthefeed.com/get-the-facts/ could save 467B (12% 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

Avoids an excessive DOM size179 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 Nodes
    179
    target < 1,500 nodes
  • DOM Depth
    11
    target < 32
  • Maximum Children
    37
    target < 60 nodes

Compressed ImagesPotential savings of 10 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

ThumbnailsURLOriginalPotential Savings
https://j3a3p9y4.stackpathcdn.com/wp-content/themes/changing-markets/img/watercolour-1.jpg50 KB9 KB (19%)
...

Uses Progressive JPEGsScore: 100 %

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 623 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 1 blocking CSS resources. This causes a delay in rendering your page.

URL
https://j3a3p9y4.stackpathcdn.com/wp-content/cache/minify/383e9.js
https://j3a3p9y4.stackpathcdn.com/wp-content/cache/minify/86a1a.css
...

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. Source: PageSpeed Insights - 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. Source: PageSpeed Insights - 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. Source: PageSpeed Insights - Learn more

Usability 75/100 Industry: Lead Gen

Key and appropriate information is provided and is easy to find on the product page e.g. APR, key benefits, etc

Fails if information is missing or hard to find.

Relevant product/service details are concise and use bullet points to make it easy for the user to skim and scan the content for understanding

Fails if content is laid out in text form and large paragraphs requiring the user to seek out the information themselves by reading large bodies of text.

Phone numbers are clickable to make callsNot applicable

Fails if missing tap to call functionality.

Links never open new browser tabs unless clearly indicated or users can back arrow to the previous page

Fails if opening new browser tabs without warning the user in advance that this will happen.

Access to instant, responsive support (web chat or phone) within office hours is available at any point

Fails if missing or hard to find contact options. Contact options should align with regional expectations.

Optional fields are clearly optionalNot applicable

Fails if it is not clear that optional fields are optional, i.e. They do not say 'optional' or they do not follow the pattern of no asterisk for optional, while compulsory fields do.

The most appropriate keyboard for the input type is provided firstNot applicable

Fails if most helpful keyboard not provided, i.e. input types text, tel, email, password, capitalization when appropiate, etc.

The website supports autofill for all form fields and the fields are tagged for the appropriate information from autofillNot applicable

Fails if fields are not tagged for efficient browser-based autofill, making users enter data that is already known either by the website or the OS. Not filling a standard field or filling fields with the wrong content, i.e. puts house number and street name into the same field when there are separate fields for each.

All mistakes made in forms are clearly highlighted in real time, and instructions for correct completion are provided in real timeNot applicable

Fails if mistakes and guidance for correct completion are not highlighted in real time and/or error messages are ambiguous or unfriendly.

Within a form, users can navigate back and forth between steps/pages without losing previously inputted informationNot applicable

Fails if a user backtracks and previously entered data is lost.

PWA / Best Practices 82/100

Avoids Application Cache

Application Cache is deprecated. Source: Lighthouse - Learn more

Avoids WebSQL DB

Web SQL is deprecated. Consider using IndexedDB instead. Source: Lighthouse - Learn more

Avoids requesting the geolocation permission on page load

Users are mistrustful of or confused by sites that request their location without context. Consider tying the request to user gestures instead. Source: Lighthouse - Learn more

robots.txt is valid

If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Source: Lighthouse

Avoids requesting the notification permission on page load

Users are mistrustful of or confused by sites that request to send notifications without context. Consider tying the request to user gestures instead. Source: Lighthouse - Learn more

Avoids deprecated APIs

Deprecated APIs will eventually be removed from the browser. Source: Lighthouse - Learn more

Allows to paste into password input fields

The main reason why password pasting improves security is because it helps to reduce password overload. Source: Lighthouse - Learn more

Registers a Service Worker

The service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. Source: Lighthouse - Learn more

Responds with a 200 when offline

If you're building a Progressive Web App, consider using a service worker so that your app can work offline. Source: Lighthouse - Learn more

Uses HTTPS

All sites should be protected with HTTPS, even ones that don't handle sensitive data. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Source: Lighthouse - Learn more

Redirects HTTP traffic to HTTPS

If you've already set up HTTPS, make sure that you redirect all HTTP traffic to HTTPS. Source: Lighthouse - Learn more

Uses HTTP/2 for its own resources2 requests not served via HTTP/2

HTTP/2 offers many benefits over HTTP/1.1, including binary headers, multiplexing, and server push. Source: Lighthouse - Learn more

Uses passive listeners to improve scrolling performance

Mark your touch and wheel event listeners as `passive` to improve your page's scroll performance. Source: Lighthouse - Learn more

Avoid using document.write()

For users on slow connections, external scripts dynamically injected via document.write() can delay page load by tens of seconds. Source: Lighthouse - Learn more

Manifest's short_name won't be truncated when displayed on homescreen

Make your app's short_name fewer than 12 characters to ensure that it's not truncated on homescreens. Source: Lighthouse - Learn more

Configured for a custom splash screen

A default splash screen will be constructed for your app, but satisfying these requirements guarantee a high-quality splash screen that transitions the user from tapping the home screen icon to your app's first paint. Source: Lighthouse - Learn more

User can be prompted to Install the Web App

Browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement. Source: Lighthouse - Learn more

Mobile Friendliness 60/100

Configures the viewport

This rule triggers when detecting that your page does not specify a viewport, or specifies a viewport that does not adapt to different devices. Source: PageSpeed Insights - Learn more

Content is sized correctly for the viewport

If the width of your app's content doesn't match the width of the viewport, your app might not be optimized for mobile screens. Source: Lighthouse - Learn more

Size tap targets appropriately

This rule triggers when detecting that certain tap targets (e.g. buttons, links, or form fields) may be too small or too close together for a user to easily tap on a touchscreen. Source: PageSpeed Insights - Learn more

The following tap targets are close to other nearby tap targets and may need additional spacing around them.

URL
The tap target <button class="button button-…n button--copy">fishingthefeed.com</button> is close to 1 other tap targets.
...

Uses legible font sizes

This rule triggers when detecting that text in the page is too small to be legible. Source: PageSpeed Insights - Learn more

Color Contrast is satisfactory

Low-contrast text is difficult or impossible for many users to read. Background and foreground colors should have enough contrast ratio to guarantee readability. Source: Lighthouse - Learn more

Failing Elements

ImpactSnippetTargetFailure Summary
serious<p>Fishing the Feed is a project by the Changing Markets Foundation in partnership with...</p>.footer-middle > pFix any of the following: Element has insufficient color contrast of 2.58 (foreground color: #58515e, background color: #110619, font size: 9.8pt, font weight: normal). Expected contrast ratio of 4.5:1
serious<p>© Changing Markets Foundation 2019<br> Designed and built by <a href="https://fiasco.design" title="Fiasco Design Website">Fiasco Design</a></p>.footer-bottom > pFix any of the following: Element has insufficient color contrast of 2.58 (foreground color: #58515e, background color: #110619, font size: 9.8pt, font weight: normal). Expected contrast ratio of 4.5:1
...

Performance 60/100

Speed Index

  • Speed Index
    5291.34
    target < 4500 ms

Perceptual 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

  • Time
    19.2
    seconds
  • Resources
    42
    requests
  • Bytes in
    2.1
    MB

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

  • Time
    19.9
    seconds
  • Resources
    43
    requests
  • Bytes in
    2.1
    MB

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

  • j3a3p9y4.stackpathcdn.com

  • www.fishingthefeed.com

  • platform.twitter.com

  • www.google-analytics.com

  • www.googletagmanager.com

  • syndication.twitter.com

Bytes downloaded

  • j3a3p9y4.stackpathcdn.com

  • platform.twitter.com

  • www.googletagmanager.com

  • www.fishingthefeed.com

  • www.google-analytics.com

  • syndication.twitter.com

Assets by Mime-Type

Requests

  • html

  • js

  • css

  • image

  • font

  • other

Bytes downloaded

  • html

  • js

  • css

  • image

  • font

  • other

Speed

Load time19166 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 byte3088 ms

The time from the initial request to the first byte of the response. Source: WebPagetest - Learn more

First Contentful Paint3557.196 ms

First contentful paint marks the time at which the first text/image is painted. Source: Lighthouse - Learn more

First meaningful paint4622.028 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 Idle4622.03 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 Interactive4622.03 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: 100%

This rule triggers when detecting that compressible resources were served without gzip compression. Source: WebPagetest - Learn more

Uses a CDN for all static assetsScore: 85%

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://syndication.twitter.com/settings (10 minutes)
https://www.googletagmanager.com/gtag/js?id=UA-145607346-2 (15 minutes)
https://platform.twitter.com/widgets.js?ver=1.3 (30 minutes)
https://j3a3p9y4.stackpathcdn.com/wp-content/cache/minify/3fd89.js (60 minutes)
https://j3a3p9y4.stackpathcdn.com/wp-content/cache/minify/97753.css (60 minutes)
https://j3a3p9y4.stackpathcdn.com/wp-content/cache/minify/ab3ad.js (60 minutes)
https://www.google-analytics.com/analytics.js (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. Source: PageSpeed Insights - 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. Source: PageSpeed Insights - Learn more

Minify HTML for the following resources to reduce their size by 573B (11% reduction).

URL
Minifying https://www.fishingthefeed.com/what-can-you-do/ could save 573B (11% 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

Avoids an excessive DOM size221 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 Nodes
    221
    target < 1,500 nodes
  • DOM Depth
    11
    target < 32
  • Maximum Children
    38
    target < 60 nodes

Compressed ImagesPotential savings of 28 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

ThumbnailsURLOriginalPotential Savings
https://j3a3p9y4.stackpathcdn.com/wp-content/themes/changing-markets/img/video-share.jpg25 KB18 KB (71%)
https://j3a3p9y4.stackpathcdn.com/wp-content/themes/changing-markets/img/watercolour-1.jpg50 KB9 KB (19%)
...

Uses Progressive JPEGsScore: 22 %

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 623 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 1 blocking CSS resources. This causes a delay in rendering your page.

URL
https://j3a3p9y4.stackpathcdn.com/wp-content/cache/minify/ab3ad.js
https://j3a3p9y4.stackpathcdn.com/wp-content/cache/minify/97753.css
...

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. Source: PageSpeed Insights - 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. Source: PageSpeed Insights - 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. Source: PageSpeed Insights - Learn more

Usability 75/100 Industry: Lead Gen

Key and appropriate information is provided and is easy to find on the product page e.g. APR, key benefits, etc

Fails if information is missing or hard to find.

Relevant product/service details are concise and use bullet points to make it easy for the user to skim and scan the content for understanding

Fails if content is laid out in text form and large paragraphs requiring the user to seek out the information themselves by reading large bodies of text.

Phone numbers are clickable to make callsNot applicable

Fails if missing tap to call functionality.

Links never open new browser tabs unless clearly indicated or users can back arrow to the previous page

Fails if opening new browser tabs without warning the user in advance that this will happen.

Access to instant, responsive support (web chat or phone) within office hours is available at any point

Fails if missing or hard to find contact options. Contact options should align with regional expectations.

Optional fields are clearly optionalNot applicable

Fails if it is not clear that optional fields are optional, i.e. They do not say 'optional' or they do not follow the pattern of no asterisk for optional, while compulsory fields do.

The most appropriate keyboard for the input type is provided firstNot applicable

Fails if most helpful keyboard not provided, i.e. input types text, tel, email, password, capitalization when appropiate, etc.

The website supports autofill for all form fields and the fields are tagged for the appropriate information from autofillNot applicable

Fails if fields are not tagged for efficient browser-based autofill, making users enter data that is already known either by the website or the OS. Not filling a standard field or filling fields with the wrong content, i.e. puts house number and street name into the same field when there are separate fields for each.

All mistakes made in forms are clearly highlighted in real time, and instructions for correct completion are provided in real timeNot applicable

Fails if mistakes and guidance for correct completion are not highlighted in real time and/or error messages are ambiguous or unfriendly.

Within a form, users can navigate back and forth between steps/pages without losing previously inputted informationNot applicable

Fails if a user backtracks and previously entered data is lost.

PWA / Best Practices 82/100

Avoids Application Cache

Application Cache is deprecated. Source: Lighthouse - Learn more

Avoids WebSQL DB

Web SQL is deprecated. Consider using IndexedDB instead. Source: Lighthouse - Learn more

Avoids requesting the geolocation permission on page load

Users are mistrustful of or confused by sites that request their location without context. Consider tying the request to user gestures instead. Source: Lighthouse - Learn more

robots.txt is valid

If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Source: Lighthouse

Avoids requesting the notification permission on page load

Users are mistrustful of or confused by sites that request to send notifications without context. Consider tying the request to user gestures instead. Source: Lighthouse - Learn more

Avoids deprecated APIs

Deprecated APIs will eventually be removed from the browser. Source: Lighthouse - Learn more

Allows to paste into password input fields

The main reason why password pasting improves security is because it helps to reduce password overload. Source: Lighthouse - Learn more

Registers a Service Worker

The service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. Source: Lighthouse - Learn more

Responds with a 200 when offline

If you're building a Progressive Web App, consider using a service worker so that your app can work offline. Source: Lighthouse - Learn more

Uses HTTPS

All sites should be protected with HTTPS, even ones that don't handle sensitive data. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Source: Lighthouse - Learn more

Redirects HTTP traffic to HTTPS

If you've already set up HTTPS, make sure that you redirect all HTTP traffic to HTTPS. Source: Lighthouse - Learn more

Uses HTTP/2 for its own resources8 requests not served via HTTP/2

HTTP/2 offers many benefits over HTTP/1.1, including binary headers, multiplexing, and server push. Source: Lighthouse - Learn more

Uses passive listeners to improve scrolling performance

Mark your touch and wheel event listeners as `passive` to improve your page's scroll performance. Source: Lighthouse - Learn more

Avoid using document.write()

For users on slow connections, external scripts dynamically injected via document.write() can delay page load by tens of seconds. Source: Lighthouse - Learn more

Manifest's short_name won't be truncated when displayed on homescreen

Make your app's short_name fewer than 12 characters to ensure that it's not truncated on homescreens. Source: Lighthouse - Learn more

Configured for a custom splash screen

A default splash screen will be constructed for your app, but satisfying these requirements guarantee a high-quality splash screen that transitions the user from tapping the home screen icon to your app's first paint. Source: Lighthouse - Learn more

User can be prompted to Install the Web App

Browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement. Source: Lighthouse - Learn more
Report created on Nov 07, 2019, 15:29 PM GMT+0 in 13 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 EnvironmentMobile