Tools & Wizards About Us
dijkstra.net screenshot

Report Summary

  • 23

    Performance

    Renders faster than
    42% of other websites

  • 92

    Accessibility

    Visual factors better than
    that of 78% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

dijkstra.net

Dijkstra Vereenigde - verpakkingsglas en laboratoriumapparatuur - Dijkstra.net

Page Load Speed

3.6 sec in total

First Response

872 ms

Resources Loaded

2.5 sec

Page Rendered

254 ms

dijkstra.net screenshot

About Website

Welcome to dijkstra.net homepage info - get ready to check Dijkstra best content for Netherlands right away, or after learning these important things about dijkstra.net

Dijkstra Vereenigde de specialist in laboratoriumapparatuur en verpakkingsglas. Een betrokken partner met een groot gevoel voor service, kwaliteit en marktbehoeften.

Visit dijkstra.net

Key Findings

We analyzed Dijkstra.net page load time and found that the first response time was 872 ms and then it took 2.8 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

dijkstra.net performance score

23

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

36/100

10%

LCP (Largest Contentful Paint)

Value5.0 s

27/100

25%

SI (Speed Index)

Value9.5 s

12/100

10%

TBT (Total Blocking Time)

Value4,370 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.16

73/100

15%

TTI (Time to Interactive)

Value19.4 s

2/100

10%

Network Requests Diagram

www.dijkstra.net

872 ms

91fc2de4d722408d482bc3227e060f61.min.css

274 ms

ec.min.css

270 ms

cb6113a4024e26a5978d02f86b501984.min.js

365 ms

css

33 ms

Our browser made a total of 22 requests to load all elements on the main page. We found that 82% of them (18 requests) were addressed to the original Dijkstra.net, 9% (2 requests) were made to Fonts.gstatic.com and 5% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (872 ms) belongs to the original domain Dijkstra.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 347.4 kB (19%)

Content Size

1.8 MB

After Optimization

1.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Dijkstra.net main page is 1.8 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. 45% of websites need less resources to load. Images take 1.6 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 86.0 kB

  • Original 112.3 kB
  • After minification 101.1 kB
  • After compression 26.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 86.0 kB or 77% of the original size.

Image Optimization

-16%

Potential reduce by 258.4 kB

  • Original 1.6 MB
  • After minification 1.3 MB

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. Obviously, Dijkstra needs image optimization as it can save up to 258.4 kB or 16% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-1%

Potential reduce by 220 B

  • Original 23.6 kB
  • After minification 23.6 kB
  • After compression 23.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.

CSS Optimization

-3%

Potential reduce by 2.8 kB

  • Original 99.4 kB
  • After minification 99.4 kB
  • After compression 96.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. Dijkstra.net has all CSS files already compressed.

Requests Breakdown

We found no issues to fix!

Requests Now

18

After Optimization

18

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.dijkstra.net

www.dijkstra.net

872 ms

91fc2de4d722408d482bc3227e060f61.min.css

91fc2de4d722408d482bc3227e060f61.min.css

274 ms

ec.min.css

ec.min.css

270 ms

cb6113a4024e26a5978d02f86b501984.min.js

cb6113a4024e26a5978d02f86b501984.min.js

365 ms

css

css

33 ms

gtm.js

gtm.js

71 ms

logo_1_.png

logo_1_.png

96 ms

Phone_icon.png

Phone_icon.png

95 ms

Mailicon.png

Mailicon.png

94 ms

Kantoor-Dijkstra-Vereenigde-Lelystad.jpg

Kantoor-Dijkstra-Vereenigde-Lelystad.jpg

542 ms

Erasmusmc.jpg

Erasmusmc.jpg

188 ms

Wageningen_university.png

Wageningen_university.png

189 ms

Amsterdam-UMC_1.png

Amsterdam-UMC_1.png

273 ms

Bobbys-Jenever_1.jpg

Bobbys-Jenever_1.jpg

274 ms

jizaRExUiTo99u79D0KEwA.ttf

jizaRExUiTo99u79D0KEwA.ttf

44 ms

jizfRExUiTo99u79B_mh0O6tKA.ttf

jizfRExUiTo99u79B_mh0O6tKA.ttf

45 ms

dijkstra-icons.woff

dijkstra-icons.woff

254 ms

foto_2.jpg

foto_2.jpg

417 ms

Dijkstra_Verpakkingen_Verpakkingsglas.jpg

Dijkstra_Verpakkingen_Verpakkingsglas.jpg

328 ms

1Gin1689.png

1Gin1689.png

859 ms

brouwerij-maallust.jpg

brouwerij-maallust.jpg

680 ms

bartender-Richard-Catz-Gin.jpg

bartender-Richard-Catz-Gin.jpg

682 ms

Accessibility Review

dijkstra.net accessibility score

92

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[role]s do not have all required [aria-*] attributes

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

Links do not have a discernible name

Best Practices

dijkstra.net best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

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

dijkstra.net SEO score

92

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

    NL

  • Language Claimed

    NL

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Dijkstra.net 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 Dijkstra.net 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

dijkstra.net

Open Graph description is not detected on the main page of Dijkstra. 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: