Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

pulse.nl

Fellowmind | Expert in Microsoft Dynamics 365, Cloud & Data

Page Load Speed

4.1 sec in total

First Response

391 ms

Resources Loaded

2.5 sec

Page Rendered

1.1 sec

pulse.nl screenshot

About Website

Click here to check amazing Pulse content. Otherwise, check out these important facts you probably never knew about pulse.nl

Fellowmind is Europees expert op het vlak van Microsoft Business Applications, Cloud Infrastructure, Data & Analytics en Modern Workplace. Kom in contact!

Visit pulse.nl

Key Findings

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

Performance Metrics

pulse.nl performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

30/100

10%

LCP (Largest Contentful Paint)

Value11.2 s

0/100

25%

SI (Speed Index)

Value11.6 s

4/100

10%

TBT (Total Blocking Time)

Value2,050 ms

7/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value17.1 s

4/100

10%

Network Requests Diagram

www.pulse.nl

391 ms

393 ms

fellowmind.css

66 ms

uc.js

134 ms

chunk-vendors.js

90 ms

Our browser made a total of 43 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Pulse.nl, 81% (35 requests) were made to Fellowmindcompany.com and 5% (2 requests) were made to Consent.cookiebot.com. The less responsive or slowest element that took the longest time to load (914 ms) relates to the external source Fellowmindcompany.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 297.8 kB (12%)

Content Size

2.6 MB

After Optimization

2.3 MB

In fact, the total size of Pulse.nl main page is 2.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. 70% of websites need less resources to load. Images take 2.3 MB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 190.3 kB

  • Original 217.1 kB
  • After minification 198.4 kB
  • After compression 26.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 190.3 kB or 88% of the original size.

Image Optimization

-4%

Potential reduce by 89.6 kB

  • Original 2.3 MB
  • After minification 2.2 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. Pulse images are well optimized though.

JavaScript Optimization

-29%

Potential reduce by 10.4 kB

  • Original 36.3 kB
  • After minification 36.3 kB
  • After compression 25.8 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 10.4 kB or 29% of the original size.

CSS Optimization

-32%

Potential reduce by 7.5 kB

  • Original 23.6 kB
  • After minification 23.6 kB
  • After compression 16.1 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. Pulse.nl needs all CSS files to be minified and compressed as it can save up to 7.5 kB or 32% of the original size.

Requests Breakdown

Number of requests can be reduced by 6 (15%)

Requests Now

40

After Optimization

34

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

Accessibility Review

pulse.nl accessibility score

76

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

Best Practices

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

Page has valid source maps

SEO Factors

pulse.nl SEO score

92

Search Engine Optimization Advices

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

    NL

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pulse.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 Pulse.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 description is not detected on the main page of Pulse. 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: