Tools & Wizards About Us
heyman.nl screenshot

Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 49% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 81

    SEO

    Google-friendlier than
    42% of websites

heyman.nl

Meubelstoffeerder in Zwolle e.o. - Heyman Stoffeerspecialisten Zwolle

Page Load Speed

3.9 sec in total

First Response

657 ms

Resources Loaded

2.9 sec

Page Rendered

358 ms

heyman.nl screenshot

About Website

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

Meubelstoffeerder in Zwolle gezocht? Kom langs bij Heyman Stoffeerspecialisten Zwolle en vraag naar de mogelijkheden!

Visit heyman.nl

Key Findings

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

heyman.nl performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.8 s

4/100

10%

LCP (Largest Contentful Paint)

Value15.0 s

0/100

25%

SI (Speed Index)

Value9.4 s

12/100

10%

TBT (Total Blocking Time)

Value6,840 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.039

100/100

15%

TTI (Time to Interactive)

Value14.5 s

9/100

10%

Network Requests Diagram

heyman.nl

657 ms

reset.css

165 ms

responsive.css

250 ms

menu.css

251 ms

jquery-1.10.1.min.js

582 ms

Our browser made a total of 33 requests to load all elements on the main page. We found that 97% of them (32 requests) were addressed to the original Heyman.nl, 3% (1 request) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Heyman.nl.

Page Optimization Overview & Recommendations

Page size can be reduced by 172.9 kB (27%)

Content Size

633.2 kB

After Optimization

460.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Heyman.nl main page is 633.2 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 20% of websites need less resources to load. Images take 450.2 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 9.9 kB

  • Original 12.6 kB
  • After minification 11.1 kB
  • After compression 2.6 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 1.5 kB, which is 12% 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 9.9 kB or 79% of the original size.

Image Optimization

-9%

Potential reduce by 39.8 kB

  • Original 450.2 kB
  • After minification 410.4 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. Heyman images are well optimized though.

JavaScript Optimization

-71%

Potential reduce by 105.1 kB

  • Original 148.9 kB
  • After minification 138.8 kB
  • After compression 43.7 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 105.1 kB or 71% of the original size.

CSS Optimization

-84%

Potential reduce by 18.0 kB

  • Original 21.6 kB
  • After minification 11.7 kB
  • After compression 3.6 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. Heyman.nl needs all CSS files to be minified and compressed as it can save up to 18.0 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 9 (29%)

Requests Now

31

After Optimization

22

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

heyman.nl

heyman.nl

657 ms

reset.css

reset.css

165 ms

responsive.css

responsive.css

250 ms

menu.css

menu.css

251 ms

jquery-1.10.1.min.js

jquery-1.10.1.min.js

582 ms

jquery.responsive-breakpoints.js

jquery.responsive-breakpoints.js

169 ms

loader.js

loader.js

170 ms

rjb1bjt.js

rjb1bjt.js

159 ms

jquery.vegas.js

jquery.vegas.js

248 ms

jquery.vegas.css

jquery.vegas.css

252 ms

Show_1.css

Show_1.css

439 ms

showtimeoverride.css

showtimeoverride.css

252 ms

jquery.cycle.all.min.js

jquery.cycle.all.min.js

690 ms

back_container.png

back_container.png

256 ms

slideshow_home_01.jpg

slideshow_home_01.jpg

86 ms

slideshow_home_02.jpg

slideshow_home_02.jpg

253 ms

slideshow_home_03.jpg

slideshow_home_03.jpg

336 ms

slideshow_home_10.jpg

slideshow_home_10.jpg

289 ms

slideshow_home_11.jpg

slideshow_home_11.jpg

499 ms

slideshow_home_13.jpg

slideshow_home_13.jpg

509 ms

slideshow_home_14.jpg

slideshow_home_14.jpg

1578 ms

back_home.png

back_home.png

84 ms

back_contact.png

back_contact.png

86 ms

back_nieuwsbrief.png

back_nieuwsbrief.png

87 ms

onzewinkel.png

onzewinkel.png

508 ms

fotogallery.png

fotogallery.png

255 ms

heyman_mobile.jpg

heyman_mobile.jpg

334 ms

icon-bellen.png

icon-bellen.png

168 ms

icon-mail.png

icon-mail.png

169 ms

icon-navigate.png

icon-navigate.png

254 ms

showtimeoverride.js

showtimeoverride.js

225 ms

loading.gif

loading.gif

295 ms

home.jpg

home.jpg

1055 ms

Accessibility Review

heyman.nl accessibility score

80

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

Links do not have a discernible name

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

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

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

heyman.nl SEO score

81

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

High

robots.txt is not valid

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

    UTF-8

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

heyman.nl

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