Tools & Wizards About Us
500e.nl screenshot

Report Summary

  • 38

    Performance

    Renders faster than
    57% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 88

    SEO

    Google-friendlier than
    65% of websites

500e.nl

NEXT Exclusives | Exclusive excellence

Page Load Speed

6.8 sec in total

First Response

774 ms

Resources Loaded

5.6 sec

Page Rendered

351 ms

500e.nl screenshot

About Website

Visit 500e.nl now to see the best up-to-date 500 E content for United States and also check out these interesting facts you probably never knew about 500e.nl

NEXT Exclusives is dé bestemming voor liefhebbers van luxe automobielen, exclusieve sportwagens en supercars.

Visit 500e.nl

Key Findings

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

Performance Metrics

500e.nl performance score

38

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.0 s

4/100

10%

LCP (Largest Contentful Paint)

Value6.1 s

12/100

25%

SI (Speed Index)

Value12.6 s

3/100

10%

TBT (Total Blocking Time)

Value480 ms

59/100

30%

CLS (Cumulative Layout Shift)

Value0.038

100/100

15%

TTI (Time to Interactive)

Value12.1 s

16/100

10%

Network Requests Diagram

500e.nl

774 ms

www.nextexclusives.nl

1615 ms

style.min.css

102 ms

styles.css

219 ms

app.css

676 ms

Our browser made a total of 55 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original 500e.nl, 71% (39 requests) were made to Nextexclusives.nl and 9% (5 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.6 sec) relates to the external source Nextexclusives.nl.

Page Optimization Overview & Recommendations

Page size can be reduced by 181.1 kB (21%)

Content Size

852.7 kB

After Optimization

671.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of 500e.nl main page is 852.7 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. 55% of websites need less resources to load. Javascripts take 389.0 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 63.2 kB

  • Original 81.5 kB
  • After minification 78.8 kB
  • After compression 18.3 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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 63.2 kB or 78% of the original size.

Image Optimization

-5%

Potential reduce by 8.6 kB

  • Original 157.5 kB
  • After minification 148.8 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. 500 E images are well optimized though.

JavaScript Optimization

-13%

Potential reduce by 51.4 kB

  • Original 389.0 kB
  • After minification 389.0 kB
  • After compression 337.5 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 51.4 kB or 13% of the original size.

CSS Optimization

-26%

Potential reduce by 57.8 kB

  • Original 224.7 kB
  • After minification 221.7 kB
  • After compression 166.9 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. 500e.nl needs all CSS files to be minified and compressed as it can save up to 57.8 kB or 26% of the original size.

Requests Breakdown

Number of requests can be reduced by 36 (77%)

Requests Now

47

After Optimization

11

  • Images
  • JavaScript
  • CSS

The browser has sent 47 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 500 E. 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 19 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

500e.nl

500e.nl

774 ms

www.nextexclusives.nl

www.nextexclusives.nl

1615 ms

style.min.css

style.min.css

102 ms

styles.css

styles.css

219 ms

app.css

app.css

676 ms

style.min.css

style.min.css

318 ms

style.css

style.css

596 ms

style.css

style.css

408 ms

grid.css

grid.css

415 ms

icons.css

icons.css

417 ms

js_composer.min.css

js_composer.min.css

621 ms

animations.css

animations.css

420 ms

grid_responsive.css

grid_responsive.css

504 ms

css

css

47 ms

style.css

style.css

513 ms

language-cookie.js

language-cookie.js

516 ms

jquery.min.js

jquery.min.js

634 ms

jquery-migrate.min.js

jquery-migrate.min.js

606 ms

slick.min.js

slick.min.js

695 ms

app.js

app.js

695 ms

libs.min.js

libs.min.js

715 ms

common.js

common.js

615 ms

jquery.smoothscroll.js

jquery.smoothscroll.js

700 ms

xdomain-data.js

xdomain-data.js

700 ms

all.css

all.css

54 ms

css

css

62 ms

background-style.css

background-style.css

713 ms

animate.css

animate.css

816 ms

style.css

style.css

817 ms

rs6.css

rs6.css

817 ms

rbtools.min.js

rbtools.min.js

1046 ms

rs6.min.js

rs6.min.js

1046 ms

index.js

index.js

851 ms

js_composer_front.min.js

js_composer_front.min.js

851 ms

ultimate_bg.js

ultimate_bg.js

851 ms

jparallax.js

jparallax.js

908 ms

jquery.vhparallax.js

jquery.vhparallax.js

952 ms

jquery.appear.js

jquery.appear.js

955 ms

custom.js

custom.js

954 ms

gtm.js

gtm.js

142 ms

Next-Exclusives-logo-457-x-50-black-2.png

Next-Exclusives-logo-457-x-50-black-2.png

275 ms

mobile-flex.jpg

mobile-flex.jpg

741 ms

nl.png

nl.png

272 ms

en.png

en.png

272 ms

de.png

de.png

271 ms

dummy.png

dummy.png

271 ms

mobile-flex.jpg

mobile-flex.jpg

1121 ms

mobile-flex.jpg

mobile-flex.jpg

912 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aXx-p7K4GLs.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aXx-p7K4GLs.woff

76 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aXx-p7K4GLs.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aXx-p7K4GLs.woff

91 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aXx-p7K4GLs.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aXx-p7K4GLs.woff

93 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aXx-p7K4GLs.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aXx-p7K4GLs.woff

92 ms

icomoon.svg

icomoon.svg

624 ms

icomoon.woff

icomoon.woff

612 ms

KFOmCnqEu92Fr1Mu4mxMKTU1Kg.woff

KFOmCnqEu92Fr1Mu4mxMKTU1Kg.woff

16 ms

Accessibility Review

500e.nl accessibility score

84

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

500e.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

SEO Factors

500e.nl SEO score

88

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

robots.txt is not valid

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    NL

  • Language Claimed

    NL

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 500e.nl can be misinterpreted by Google and other search engines. Our service has detected that Dutch is used on the page, and it matches the claimed language. Our system also found out that 500e.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

500e.nl

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