Report Summary

  • 32

    Performance

    Renders faster than
    52% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 40% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

prospex.nl

prospex

Page Load Speed

5.5 sec in total

First Response

312 ms

Resources Loaded

4.3 sec

Page Rendered

911 ms

prospex.nl screenshot

About Website

Welcome to prospex.nl homepage info - get ready to check Prospex best content right away, or after learning these important things about prospex.nl

Nieuwe B2B leads genereren? Ontdek de kracht van onze persoonlijke aanpak en ervaring bij prospex. Laat ons jouw bedrijf helpen groeien.

Visit prospex.nl

Key Findings

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

Performance Metrics

prospex.nl performance score

32

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.0 s

10/100

10%

LCP (Largest Contentful Paint)

Value11.3 s

0/100

25%

SI (Speed Index)

Value9.0 s

14/100

10%

TBT (Total Blocking Time)

Value420 ms

66/100

30%

CLS (Cumulative Layout Shift)

Value0.252

49/100

15%

TTI (Time to Interactive)

Value9.9 s

27/100

10%

Network Requests Diagram

prospex.nl

312 ms

www.prospex.nl

1300 ms

gtm.js

68 ms

font-awesome.min.css

49 ms

bootstrap.min.css

199 ms

Our browser made a total of 61 requests to load all elements on the main page. We found that 66% of them (40 requests) were addressed to the original Prospex.nl, 10% (6 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Prospex.nl.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.1 MB (16%)

Content Size

7.2 MB

After Optimization

6.0 MB

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

HTML Optimization

-83%

Potential reduce by 68.3 kB

  • Original 82.2 kB
  • After minification 69.7 kB
  • After compression 13.9 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 12.5 kB, which is 15% 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 68.3 kB or 83% of the original size.

Image Optimization

-15%

Potential reduce by 1.0 MB

  • Original 6.9 MB
  • After minification 5.8 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, Prospex needs image optimization as it can save up to 1.0 MB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-7%

Potential reduce by 9.7 kB

  • Original 141.9 kB
  • After minification 141.9 kB
  • After compression 132.2 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

-8%

Potential reduce by 4.5 kB

  • Original 59.0 kB
  • After minification 59.0 kB
  • After compression 54.5 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. Prospex.nl has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 25 (50%)

Requests Now

50

After Optimization

25

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

Accessibility Review

prospex.nl accessibility score

74

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.

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

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

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

prospex.nl best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

prospex.nl SEO score

100

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

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 Prospex.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 Prospex.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 Prospex. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: