Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 49% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

prontoxl.com

ProntoXL | Voetbalschoenen Trainingspakken Sneakers

Page Load Speed

3.2 sec in total

First Response

570 ms

Resources Loaded

2.3 sec

Page Rendered

275 ms

prontoxl.com screenshot

About Website

Click here to check amazing ProntoXL content. Otherwise, check out these important facts you probably never knew about prontoxl.com

Bestel je voetbalbalschoenen, Presentatiepakken, Nike Air en Sneakers zeer voordelig op de voetbalshop van ProntoXL, Bestel voor 17.00 en krijg je bestelling de volgende werkdag in huis.

Visit prontoxl.com

Key Findings

We analyzed Prontoxl.com page load time and found that the first response time was 570 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

prontoxl.com performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.3 s

7/100

10%

LCP (Largest Contentful Paint)

Value8.4 s

2/100

25%

SI (Speed Index)

Value7.8 s

23/100

10%

TBT (Total Blocking Time)

Value1,040 ms

26/100

30%

CLS (Cumulative Layout Shift)

Value0.46

19/100

15%

TTI (Time to Interactive)

Value11.9 s

16/100

10%

Network Requests Diagram

www.prontoxl.nl

570 ms

analytics.js

60 ms

gtm.js

101 ms

fbevents.js

70 ms

169837033-3185.css

130 ms

Our browser made a total of 48 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Prontoxl.com, 6% (3 requests) were made to Google-analytics.com and 6% (3 requests) were made to Connect.facebook.net. The less responsive or slowest element that took the longest time to load (641 ms) relates to the external source 19d8ae6c9a4142398d7a406ed605681e.objectstore.eu.

Page Optimization Overview & Recommendations

Page size can be reduced by 479.8 kB (38%)

Content Size

1.3 MB

After Optimization

795.9 kB

In fact, the total size of Prontoxl.com 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 461.0 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 73.0 kB

  • Original 94.5 kB
  • After minification 94.5 kB
  • After compression 21.5 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 73.0 kB or 77% of the original size.

Image Optimization

-6%

Potential reduce by 25.8 kB

  • Original 461.0 kB
  • After minification 435.2 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. ProntoXL images are well optimized though.

JavaScript Optimization

-13%

Potential reduce by 42.8 kB

  • Original 326.5 kB
  • After minification 326.5 kB
  • After compression 283.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 42.8 kB or 13% of the original size.

CSS Optimization

-86%

Potential reduce by 338.2 kB

  • Original 393.7 kB
  • After minification 386.2 kB
  • After compression 55.6 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. Prontoxl.com needs all CSS files to be minified and compressed as it can save up to 338.2 kB or 86% of the original size.

Requests Breakdown

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

Requests Now

40

After Optimization

26

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

Accessibility Review

prontoxl.com accessibility score

80

Accessibility Issues

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

Buttons do not have an accessible name

High

Links do not have a discernible name

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

[id] attributes on active, focusable elements are not unique

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

prontoxl.com best practices score

75

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

prontoxl.com 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 Prontoxl.com 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 Prontoxl.com 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 ProntoXL. 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: