Report Summary

  • 52

    Performance

    Renders faster than
    71% of other websites

  • 97

    Accessibility

    Visual factors better than
    that of 93% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    82% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

exonet.nl

Exonet - Follow the future

Page Load Speed

2.3 sec in total

First Response

282 ms

Resources Loaded

1.8 sec

Page Rendered

234 ms

exonet.nl screenshot

About Website

Click here to check amazing Exonet content for Netherlands. Otherwise, check out these important facts you probably never knew about exonet.nl

Wij zijn Exonet: dé stille kracht achter duizenden bedrijfskritische websites en applicaties. Wat zo'n 17 jaar geleden begon met twee techneuten en een passie, is uitgegroeid tot één van de beste...

Visit exonet.nl

Key Findings

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

Performance Metrics

exonet.nl performance score

52

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

60/100

10%

LCP (Largest Contentful Paint)

Value8.7 s

1/100

25%

SI (Speed Index)

Value3.7 s

86/100

10%

TBT (Total Blocking Time)

Value610 ms

49/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value5.3 s

73/100

10%

Network Requests Diagram

exonet.nl

282 ms

www.exonet.nl

578 ms

style.css

255 ms

themepunch.css

290 ms

jquery.min.js

345 ms

Our browser made a total of 32 requests to load all elements on the main page. We found that 94% of them (30 requests) were addressed to the original Exonet.nl, 6% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (578 ms) belongs to the original domain Exonet.nl.

Page Optimization Overview & Recommendations

Page size can be reduced by 506.8 kB (56%)

Content Size

906.3 kB

After Optimization

399.5 kB

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

HTML Optimization

-76%

Potential reduce by 12.1 kB

  • Original 16.1 kB
  • After minification 14.1 kB
  • After compression 3.9 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 1.9 kB, which is 12% 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 12.1 kB or 76% of the original size.

Image Optimization

-1%

Potential reduce by 2.3 kB

  • Original 266.0 kB
  • After minification 263.7 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. Exonet images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 180.3 kB

  • Original 281.1 kB
  • After minification 275.2 kB
  • After compression 100.7 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 180.3 kB or 64% of the original size.

CSS Optimization

-91%

Potential reduce by 312.0 kB

  • Original 343.2 kB
  • After minification 262.7 kB
  • After compression 31.2 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. Exonet.nl needs all CSS files to be minified and compressed as it can save up to 312.0 kB or 91% of the original size.

Requests Breakdown

Number of requests can be reduced by 14 (47%)

Requests Now

30

After Optimization

16

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

Accessibility Review

exonet.nl accessibility score

97

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.

Best Practices

exonet.nl best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

exonet.nl SEO score

100

Search Engine Optimization Advices

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

    NL

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Exonet.nl can be misinterpreted by Google and other search engines. Our service has detected that Dutch is used on the page, and it does not match the claimed English language. Our system also found out that Exonet.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 description is not detected on the main page of Exonet. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: