Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 48% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

trekpleister.nl

Trekpleister | Homepage

Page Load Speed

2.8 sec in total

First Response

336 ms

Resources Loaded

2.1 sec

Page Rendered

346 ms

trekpleister.nl screenshot

About Website

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

Shop online bij voordelige buurtdrogist Trekpleister. Waar kunnen we je blij mee maken?

Visit trekpleister.nl

Key Findings

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

trekpleister.nl performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value11.5 s

0/100

10%

LCP (Largest Contentful Paint)

Value15.5 s

0/100

25%

SI (Speed Index)

Value12.4 s

3/100

10%

TBT (Total Blocking Time)

Value4,840 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.01

100/100

15%

TTI (Time to Interactive)

Value19.1 s

3/100

10%

Network Requests Diagram

trekpleister.nl

336 ms

www.trekpleister.nl

831 ms

General.css

603 ms

Configuration.css

350 ms

jquery-1.4.1.min.js

597 ms

Our browser made a total of 59 requests to load all elements on the main page. We found that 95% of them (56 requests) were addressed to the original Trekpleister.nl, 5% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (831 ms) belongs to the original domain Trekpleister.nl.

Page Optimization Overview & Recommendations

Page size can be reduced by 741.0 kB (46%)

Content Size

1.6 MB

After Optimization

860.9 kB

In fact, the total size of Trekpleister.nl main page is 1.6 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 732.4 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 101.9 kB

  • Original 124.2 kB
  • After minification 101.2 kB
  • After compression 22.3 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. This page needs HTML code to be minified as it can gain 23.0 kB, which is 19% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 101.9 kB or 82% of the original size.

Image Optimization

-5%

Potential reduce by 34.1 kB

  • Original 732.4 kB
  • After minification 698.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. Trekpleister images are well optimized though.

JavaScript Optimization

-80%

Potential reduce by 519.6 kB

  • Original 645.6 kB
  • After minification 475.4 kB
  • After compression 126.0 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 519.6 kB or 80% of the original size.

CSS Optimization

-86%

Potential reduce by 85.4 kB

  • Original 99.7 kB
  • After minification 70.8 kB
  • After compression 14.3 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. Trekpleister.nl needs all CSS files to be minified and compressed as it can save up to 85.4 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 17 (30%)

Requests Now

57

After Optimization

40

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

Accessibility Review

trekpleister.nl accessibility score

79

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

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

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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

trekpleister.nl SEO score

83

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

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    NL

  • Language Claimed

    N/A

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Trekpleister.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 Trekpleister.nl main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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