Tools & Wizards About Us
zapr.nl screenshot

Report Summary

  • 0

    Performance

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 58

    SEO

    Google-friendlier than
    20% of websites

zapr.nl

Deze domeinnaam is geregistreerd door een klant van Yourhosting.nl

Page Load Speed

3.4 sec in total

First Response

275 ms

Resources Loaded

3 sec

Page Rendered

131 ms

zapr.nl screenshot

About Website

Visit zapr.nl now to see the best up-to-date Zapr content and also check out these interesting facts you probably never knew about zapr.nl

GitLab Community Edition

Visit zapr.nl

Key Findings

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

zapr.nl performance score

0

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value0

0/100

10%

LCP (Largest Contentful Paint)

Value0

0/100

25%

SI (Speed Index)

Value0

0/100

10%

TBT (Total Blocking Time)

Value0

0/100

30%

CLS (Cumulative Layout Shift)

Value0.066

97/100

15%

TTI (Time to Interactive)

Value0

0/100

10%

Network Requests Diagram

zapr.nl

275 ms

gitlab.driebit.nl

513 ms

sign_in

188 ms

application-9880f992b4a3c109f2a12a3f4553d0fe.css

394 ms

application-cd4e557b2d6d44b68c2445862d96def8.js

1008 ms

Our browser made a total of 10 requests to load all elements on the main page. We found that 10% of them (1 request) were addressed to the original Zapr.nl, 90% (9 requests) were made to Gitlab.driebit.nl. The less responsive or slowest element that took the longest time to load (1 sec) relates to the external source Gitlab.driebit.nl.

Page Optimization Overview & Recommendations

Page size can be reduced by 975.0 kB (71%)

Content Size

1.4 MB

After Optimization

405.8 kB

  • HTML
  • JavaScript

In fact, the total size of Zapr.nl main page is 1.4 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. 15% of websites need less resources to load. Javascripts take 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-70%

Potential reduce by 24.9 kB

  • Original 35.3 kB
  • After minification 35.2 kB
  • After compression 10.4 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 24.9 kB or 70% of the original size.

JavaScript Optimization

-71%

Potential reduce by 950.1 kB

  • Original 1.3 MB
  • After minification 1.3 MB
  • After compression 395.4 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 950.1 kB or 71% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

3

After Optimization

3

  • JavaScript
  • CSS

The browser has sent 3 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Zapr. According to our analytics all requests are already optimized.

Network Requests Diagram

zapr.nl

zapr.nl

275 ms

gitlab.driebit.nl

gitlab.driebit.nl

513 ms

sign_in

sign_in

188 ms

application-9880f992b4a3c109f2a12a3f4553d0fe.css

application-9880f992b4a3c109f2a12a3f4553d0fe.css

394 ms

application-cd4e557b2d6d44b68c2445862d96def8.js

application-cd4e557b2d6d44b68c2445862d96def8.js

1008 ms

SourceSansPro-Regular.ttf-62b8d062684da245eb4cd31ac6e0e3ad.woff

SourceSansPro-Regular.ttf-62b8d062684da245eb4cd31ac6e0e3ad.woff

376 ms

SourceSansPro-Light.ttf-e1fe6f1a6872032ae82b70da3084ec6f.woff

SourceSansPro-Light.ttf-e1fe6f1a6872032ae82b70da3084ec6f.woff

234 ms

SourceSansPro-Semibold.ttf-f599cbfb81a904018c0ce5890f39595c.woff

SourceSansPro-Semibold.ttf-f599cbfb81a904018c0ce5890f39595c.woff

627 ms

SourceSansPro-Bold.ttf-5be8fe4ffce8ff2ddf7aa4cefdf763b5.woff

SourceSansPro-Bold.ttf-5be8fe4ffce8ff2ddf7aa4cefdf763b5.woff

662 ms

print-2cb1262fb60ceb73f2fe76fd1a61dccf.css

print-2cb1262fb60ceb73f2fe76fd1a61dccf.css

93 ms

Accessibility Review

zapr.nl accessibility score

68

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

<frame> or <iframe> elements do not have a title

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

zapr.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

High

Page has valid source maps

SEO Factors

zapr.nl SEO score

58

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

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Zapr.nl can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Zapr.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

zapr.nl

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