Report Summary

  • 40

    Performance

    Renders faster than
    61% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    57% of websites

  • 96

    SEO

    Google-friendlier than
    91% of websites

blinker.nl

Prettige software voor e-mail marketing automation | Spotler

Page Load Speed

4.4 sec in total

First Response

454 ms

Resources Loaded

3.4 sec

Page Rendered

550 ms

blinker.nl screenshot

About Website

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

Spotler biedt prettige software voor geavanceerde e-mail marketing automation. Wij maken persoonlijke en relevante communicatie makkelijk. Lees meer!

Visit blinker.nl

Key Findings

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

blinker.nl performance score

40

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

28/100

10%

LCP (Largest Contentful Paint)

Value3.8 s

56/100

25%

SI (Speed Index)

Value5.9 s

49/100

10%

TBT (Total Blocking Time)

Value2,270 ms

6/100

30%

CLS (Cumulative Layout Shift)

Value0.031

100/100

15%

TTI (Time to Interactive)

Value13.1 s

12/100

10%

Network Requests Diagram

blinker.nl

454 ms

www.blinker.nl

183 ms

jquery-1.7.1.js

124 ms

public_common.css

148 ms

font-awesome.min.css

74 ms

Our browser made a total of 100 requests to load all elements on the main page. We found that 67% of them (67 requests) were addressed to the original Blinker.nl, 12% (12 requests) were made to Cdn2.hubspot.net and 3% (3 requests) were made to Static.hsstatic.net. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Blinker.nl.

Page Optimization Overview & Recommendations

Page size can be reduced by 557.8 kB (31%)

Content Size

1.8 MB

After Optimization

1.2 MB

In fact, the total size of Blinker.nl 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. 40% of websites need less resources to load. Images take 1.0 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 91.8 kB

  • Original 106.3 kB
  • After minification 95.6 kB
  • After compression 14.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 91.8 kB or 86% of the original size.

Image Optimization

-1%

Potential reduce by 13.4 kB

  • Original 1.0 MB
  • After minification 1.0 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. Blinker images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 314.1 kB

  • Original 488.4 kB
  • After minification 487.0 kB
  • After compression 174.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 314.1 kB or 64% of the original size.

CSS Optimization

-85%

Potential reduce by 138.4 kB

  • Original 163.8 kB
  • After minification 162.8 kB
  • After compression 25.4 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. Blinker.nl needs all CSS files to be minified and compressed as it can save up to 138.4 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 32 (34%)

Requests Now

93

After Optimization

61

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

Accessibility Review

blinker.nl accessibility score

82

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

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

Heading elements are not in a sequentially-descending order

Best Practices

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

blinker.nl SEO score

96

Search Engine Optimization Advices

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

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Blinker.nl can be misinterpreted by Google and other search engines. Our service has detected that Dutch is used on the page, and it does not match the claimed English language. Our system also found out that Blinker.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 Blinker. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: