Tools & Wizards About Us
sparta.nl screenshot

Report Summary

  • 11

    Performance

    Renders faster than
    24% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 76

    SEO

    Google-friendlier than
    35% of websites

sparta.nl

Sparta E-bikes | Geef power aan je ritten met een e-bike.

Page Load Speed

2.5 sec in total

First Response

358 ms

Resources Loaded

1.8 sec

Page Rendered

376 ms

sparta.nl screenshot

About Website

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

Voel de vrijheid van fietsen op een e-bike. Sparta biedt innovatieve e-bikes voor elk gebruik. Bekijk alle e-bikes of zoek een Sparta dealer.

Visit sparta.nl

Key Findings

We analyzed Sparta.nl page load time and found that the first response time was 358 ms and then it took 2.2 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

sparta.nl performance score

11

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

43/100

10%

LCP (Largest Contentful Paint)

Value7.2 s

5/100

25%

SI (Speed Index)

Value10.4 s

8/100

10%

TBT (Total Blocking Time)

Value3,030 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.375

28/100

15%

TTI (Time to Interactive)

Value21.9 s

1/100

10%

Network Requests Diagram

sparta.nl

358 ms

539 ms

fonts.css

182 ms

otSDKStub.js

52 ms

065157e3-1170-4d4e-94b7-9333e0cee6b6.json

38 ms

Our browser made a total of 15 requests to load all elements on the main page. We found that 7% of them (1 request) were addressed to the original Sparta.nl, 40% (6 requests) were made to Spartabikes.com and 20% (3 requests) were made to Cdn.cookielaw.org. The less responsive or slowest element that took the longest time to load (543 ms) relates to the external source Spartabikes.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 99.7 kB (33%)

Content Size

298.9 kB

After Optimization

199.2 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Sparta.nl main page is 298.9 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. 30% of websites need less resources to load. HTML takes 128.2 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 99.7 kB

  • Original 128.2 kB
  • After minification 128.1 kB
  • After compression 28.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 99.7 kB or 78% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 63.3 kB
  • After minification 63.3 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. Sparta images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 45 B

  • Original 107.4 kB
  • After minification 107.4 kB
  • After compression 107.3 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. This website has mostly compressed JavaScripts.

Requests Breakdown

Number of requests can be reduced by 7 (58%)

Requests Now

12

After Optimization

5

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

sparta.nl

sparta.nl

358 ms

539 ms

fonts.css

fonts.css

182 ms

otSDKStub.js

otSDKStub.js

52 ms

065157e3-1170-4d4e-94b7-9333e0cee6b6.json

065157e3-1170-4d4e-94b7-9333e0cee6b6.json

38 ms

webpack-runtime-49990459a781992fb6fe.js

webpack-runtime-49990459a781992fb6fe.js

225 ms

framework-032858f33a322618f0e2.js

framework-032858f33a322618f0e2.js

359 ms

app-bc9801b755258e0c1641.js

app-bc9801b755258e0c1641.js

543 ms

location

location

37 ms

otBannerSdk.js

otBannerSdk.js

24 ms

gtm.js

gtm.js

86 ms

filters:quality(70)

filters:quality(70)

21 ms

sprite-flags-48x48.png

sprite-flags-48x48.png

397 ms

web-vitals.iife.js

web-vitals.iife.js

36 ms

web-vitals.iife.js

web-vitals.iife.js

35 ms

Accessibility Review

sparta.nl accessibility score

75

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

Form elements do not have associated labels

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

High

Heading elements are not in a sequentially-descending order

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

sparta.nl best practices score

83

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

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

sparta.nl SEO score

76

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

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 doesn't use legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    NL

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Sparta.nl can be misinterpreted by Google and other search engines. Our service has detected that Dutch is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Sparta.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

sparta.nl

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