Report Summary

  • 50

    Performance

    Renders faster than
    68% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

loket.nl

Salarisadministratie en HR: alles in één complete app · Loket.nl

Page Load Speed

3.7 sec in total

First Response

219 ms

Resources Loaded

2.7 sec

Page Rendered

796 ms

About Website

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

Je salarisadministratie in een handomdraai geregeld en slimme HR-mogelijkheden: alles in één online applicatie. Ontdek een wereld vol mogelijkheden.

Visit loket.nl

Key Findings

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

Performance Metrics

loket.nl performance score

50

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

45/100

10%

LCP (Largest Contentful Paint)

Value11.5 s

0/100

25%

SI (Speed Index)

Value7.2 s

30/100

10%

TBT (Total Blocking Time)

Value240 ms

86/100

30%

CLS (Cumulative Layout Shift)

Value0.008

100/100

15%

TTI (Time to Interactive)

Value11.6 s

18/100

10%

Network Requests Diagram

loket.nl

219 ms

www.loket.nl

618 ms

jquery.min.js

94 ms

jquery-migrate.min.js

187 ms

script.js

277 ms

Our browser made a total of 87 requests to load all elements on the main page. We found that all of those requests were addressed to Loket.nl and no external sources were called. The less responsive or slowest element that took the longest time to load (947 ms) belongs to the original domain Loket.nl.

Page Optimization Overview & Recommendations

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

Content Size

1.3 MB

After Optimization

882.6 kB

In fact, the total size of Loket.nl 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 609.1 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 404.7 kB

  • Original 481.5 kB
  • After minification 475.0 kB
  • After compression 76.8 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 404.7 kB or 84% of the original size.

Image Optimization

-1%

Potential reduce by 8.9 kB

  • Original 609.1 kB
  • After minification 600.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. Loket images are well optimized though.

JavaScript Optimization

-10%

Potential reduce by 23.7 kB

  • Original 229.3 kB
  • After minification 229.3 kB
  • After compression 205.6 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 39 (50%)

Requests Now

78

After Optimization

39

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

Accessibility Review

loket.nl accessibility score

88

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.

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

ARIA IDs are not unique

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

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

loket.nl 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

    NL

  • Language Claimed

    NL

  • Encoding

    UTF-8

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

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