Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 69% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 93

    SEO

    Google-friendlier than
    84% of websites

fail.nl

TransIP - Reserved domain

Page Load Speed

2.8 sec in total

First Response

301 ms

Resources Loaded

2.2 sec

Page Rendered

268 ms

fail.nl screenshot

About Website

Welcome to fail.nl homepage info - get ready to check Fail best content for Netherlands right away, or after learning these important things about fail.nl

TransIP - Reserved domain

Visit fail.nl

Key Findings

We analyzed Fail.nl page load time and found that the first response time was 301 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

fail.nl performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.7 s

5/100

10%

LCP (Largest Contentful Paint)

Value15.4 s

0/100

25%

SI (Speed Index)

Value9.8 s

10/100

10%

TBT (Total Blocking Time)

Value2,040 ms

7/100

30%

CLS (Cumulative Layout Shift)

Value0.003

100/100

15%

TTI (Time to Interactive)

Value15.0 s

7/100

10%

Network Requests Diagram

fail.nl

301 ms

www.fail.nl

722 ms

jquery-1.11.0.min.js

14 ms

jquery-migrate-1.2.1.min.js

25 ms

global.functions.js

200 ms

Our browser made a total of 58 requests to load all elements on the main page. We found that 53% of them (31 requests) were addressed to the original Fail.nl, 22% (13 requests) were made to Content.fail.nl and 5% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (817 ms) belongs to the original domain Fail.nl.

Page Optimization Overview & Recommendations

Page size can be reduced by 646.6 kB (50%)

Content Size

1.3 MB

After Optimization

648.9 kB

In fact, the total size of Fail.nl main page is 1.3 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 55% of websites need less resources to load. Images take 559.2 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 37.9 kB

  • Original 47.0 kB
  • After minification 38.9 kB
  • After compression 9.1 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. This page needs HTML code to be minified as it can gain 8.1 kB, which is 17% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 37.9 kB or 81% of the original size.

Image Optimization

-5%

Potential reduce by 29.6 kB

  • Original 559.2 kB
  • After minification 529.6 kB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Fail images are well optimized though.

JavaScript Optimization

-78%

Potential reduce by 265.8 kB

  • Original 338.9 kB
  • After minification 242.4 kB
  • After compression 73.1 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 265.8 kB or 78% of the original size.

CSS Optimization

-89%

Potential reduce by 313.4 kB

  • Original 350.4 kB
  • After minification 299.4 kB
  • After compression 37.0 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Fail.nl needs all CSS files to be minified and compressed as it can save up to 313.4 kB or 89% of the original size.

Requests Breakdown

Number of requests can be reduced by 24 (48%)

Requests Now

50

After Optimization

26

The browser has sent 50 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fail. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

fail.nl accessibility score

88

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

fail.nl best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

fail.nl SEO score

93

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    NL

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fail.nl can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Dutch language. Our system also found out that Fail.nl main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

Open Graph data is detected on the main page of Fail. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: