Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

fleetkaart.nl

Fleet Tankpas voor bedrijven - Diesel Card Service

Page Load Speed

3.6 sec in total

First Response

181 ms

Resources Loaded

3.1 sec

Page Rendered

324 ms

fleetkaart.nl screenshot

About Website

Welcome to fleetkaart.nl homepage info - get ready to check Fleet Kaart best content right away, or after learning these important things about fleetkaart.nl

Wij bieden tankkaarten van Esso, EDC en Fleetcard voor bedrijven

Visit fleetkaart.nl

Key Findings

We analyzed Fleetkaart.nl page load time and found that the first response time was 181 ms and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

fleetkaart.nl performance score

0

Network Requests Diagram

fleetkaart.nl

181 ms

www.fleetcard.nl

284 ms

style.css

306 ms

css

25 ms

font-awesome.css

6 ms

Our browser made a total of 83 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Fleetkaart.nl, 61% (51 requests) were made to Fleetcard.nl and 6% (5 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Fleetcard.nl.

Page Optimization Overview & Recommendations

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

Content Size

1.3 MB

After Optimization

644.5 kB

In fact, the total size of Fleetkaart.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. 40% of websites need less resources to load. Javascripts take 470.7 kB which makes up the majority of the site volume.

HTML Optimization

-70%

Potential reduce by 14.6 kB

  • Original 20.7 kB
  • After minification 18.0 kB
  • After compression 6.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 2.7 kB, which is 13% 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 14.6 kB or 70% of the original size.

Image Optimization

-1%

Potential reduce by 5.1 kB

  • Original 460.7 kB
  • After minification 455.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. Fleet Kaart images are well optimized though.

JavaScript Optimization

-71%

Potential reduce by 335.0 kB

  • Original 470.7 kB
  • After minification 449.9 kB
  • After compression 135.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 335.0 kB or 71% of the original size.

CSS Optimization

-86%

Potential reduce by 285.5 kB

  • Original 332.6 kB
  • After minification 224.7 kB
  • After compression 47.1 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. Fleetkaart.nl needs all CSS files to be minified and compressed as it can save up to 285.5 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 53 (73%)

Requests Now

73

After Optimization

20

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

SEO Factors

fleetkaart.nl SEO score

0

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 Fleetkaart.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 Fleetkaart.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 Fleet Kaart. 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: