Tools & Wizards About Us
premiumhuis.com screenshot

Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 88% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

premiumhuis.com

Huis verbouwen | herringbone parquet | Premium Huis B.V.

Page Load Speed

7.2 sec in total

First Response

499 ms

Resources Loaded

6.3 sec

Page Rendered

363 ms

premiumhuis.com screenshot

About Website

Welcome to premiumhuis.com homepage info - get ready to check Premium Huis best content right away, or after learning these important things about premiumhuis.com

Met de hulp van Aannemersbedrijf Den Haag kun je bouwen uw droomhuis meer aantrekkelijk en mooi. Premium Huis is gespecialiseerd in projectbouw, reparatie en afweking van middenklasse tot de elite.

Visit premiumhuis.com

Key Findings

We analyzed Premiumhuis.com page load time and found that the first response time was 499 ms and then it took 6.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

premiumhuis.com performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

13/100

10%

LCP (Largest Contentful Paint)

Value9.5 s

0/100

25%

SI (Speed Index)

Value12.4 s

3/100

10%

TBT (Total Blocking Time)

Value720 ms

41/100

30%

CLS (Cumulative Layout Shift)

Value0.563

12/100

15%

TTI (Time to Interactive)

Value9.1 s

33/100

10%

Network Requests Diagram

premiumhuis.com

499 ms

premiumhuis.com

1020 ms

css2

44 ms

jquery.fancybox.min.css

30 ms

style.min.css

501 ms

Our browser made a total of 75 requests to load all elements on the main page. We found that 85% of them (64 requests) were addressed to the original Premiumhuis.com, 9% (7 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Premiumhuis.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 270.6 kB (33%)

Content Size

811.4 kB

After Optimization

540.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Premiumhuis.com main page is 811.4 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. 70% of websites need less resources to load. HTML takes 250.2 kB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 220.0 kB

  • Original 250.2 kB
  • After minification 245.9 kB
  • After compression 30.2 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 220.0 kB or 88% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 245.5 kB
  • After minification 245.5 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. Premium Huis images are well optimized though.

JavaScript Optimization

-19%

Potential reduce by 33.2 kB

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

CSS Optimization

-12%

Potential reduce by 17.4 kB

  • Original 139.4 kB
  • After minification 138.7 kB
  • After compression 122.0 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. Premiumhuis.com needs all CSS files to be minified and compressed as it can save up to 17.4 kB or 12% of the original size.

Requests Breakdown

Number of requests can be reduced by 52 (79%)

Requests Now

66

After Optimization

14

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

premiumhuis.com

premiumhuis.com

499 ms

premiumhuis.com

premiumhuis.com

1020 ms

css2

css2

44 ms

jquery.fancybox.min.css

jquery.fancybox.min.css

30 ms

style.min.css

style.min.css

501 ms

classic-themes.min.css

classic-themes.min.css

741 ms

styles.css

styles.css

741 ms

cf7mls.css

cf7mls.css

747 ms

animate.min.css

animate.min.css

992 ms

styles.css

styles.css

753 ms

cookie-law-info-public.css

cookie-law-info-public.css

755 ms

cookie-law-info-gdpr.css

cookie-law-info-gdpr.css

985 ms

jquery.datetimepicker.min.css

jquery.datetimepicker.min.css

987 ms

owl.carousel.min.css

owl.carousel.min.css

995 ms

psac-public.css

psac-public.css

1002 ms

dashicons.min.css

dashicons.min.css

1256 ms

rmp-menu.css

rmp-menu.css

1230 ms

front-flex.min.css

front-flex.min.css

1232 ms

ivory-search.min.css

ivory-search.min.css

1237 ms

style_nl_nl.css

style_nl_nl.css

1490 ms

style.css

style.css

1996 ms

pum-site-styles.css

pum-site-styles.css

1476 ms

jquery.min.js

jquery.min.js

1721 ms

jquery-migrate.min.js

jquery-migrate.min.js

1483 ms

cookie-law-info-public.js

cookie-law-info-public.js

1722 ms

ivory-ajax-search.min.css

ivory-ajax-search.min.css

1726 ms

sow-button-flat-5a0d3583a2c6-10.css

sow-button-flat-5a0d3583a2c6-10.css

1734 ms

style.css

style.css

1756 ms

sow-layout-slider-default-2cc0c8ebe0e6-10.css

sow-layout-slider-default-2cc0c8ebe0e6-10.css

1964 ms

slider.css

slider.css

1964 ms

sow-headline-default-cd6f1e4bca77-10.css

sow-headline-default-cd6f1e4bca77-10.css

1972 ms

sow-button-flat-5c72a2991170-10.css

sow-button-flat-5c72a2991170-10.css

1982 ms

cookie-law-info-table.css

cookie-law-info-table.css

2132 ms

cf7mls.js

cf7mls.js

2230 ms

index.js

index.js

2230 ms

index.js

index.js

2232 ms

jquery.datetimepicker.full.min.js

jquery.datetimepicker.full.min.js

2477 ms

datetimepicker.js

datetimepicker.js

2248 ms

rmp-menu.js

rmp-menu.js

2272 ms

primary-navigation.js

primary-navigation.js

1960 ms

responsive-embeds.js

responsive-embeds.js

1727 ms

core.min.js

core.min.js

1744 ms

pum-site-scripts.js

pum-site-scripts.js

1750 ms

hoverIntent.min.js

hoverIntent.min.js

1780 ms

maxmegamenu.js

maxmegamenu.js

1951 ms

ivory-search.min.js

ivory-search.min.js

1727 ms

ivory-ajax-search.min.js

ivory-ajax-search.min.js

1743 ms

jquery.cycle.min.js

jquery.cycle.min.js

1739 ms

jquery.slider.min.js

jquery.slider.min.js

1752 ms

jquery.cycle.swipe.min.js

jquery.cycle.swipe.min.js

1782 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

1721 ms

css

css

24 ms

fbevents.js

fbevents.js

171 ms

rmp-menu.css

rmp-menu.css

888 ms

premiumlogo.svg

premiumlogo.svg

905 ms

spinner.gif

spinner.gif

909 ms

arrow-right-menu.svg

arrow-right-menu.svg

923 ms

makelardij-icon.svg

makelardij-icon.svg

962 ms

verbouwing-icon.svg

verbouwing-icon.svg

1126 ms

materialen-icon.svg

materialen-icon.svg

1134 ms

premiumlogo.svg

premiumlogo.svg

1151 ms

phone.svg

phone.svg

1155 ms

mail.svg

mail.svg

1172 ms

marker.svg

marker.svg

1213 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaooCP.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaooCP.ttf

39 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtaorCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtaorCIPrQ.ttf

51 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpYCP.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpYCP.ttf

75 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pYCP.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pYCP.ttf

86 ms

va9E4kDNxMZdWfMOD5VfkA.ttf

va9E4kDNxMZdWfMOD5VfkA.ttf

107 ms

va9B4kDNxMZdWfMOD5VnSKzuQQ.ttf

va9B4kDNxMZdWfMOD5VnSKzuQQ.ttf

107 ms

va9B4kDNxMZdWfMOD5VnLK3uQQ.ttf

va9B4kDNxMZdWfMOD5VnLK3uQQ.ttf

105 ms

polyfills.js

polyfills.js

956 ms

1-3.jpg

1-3.jpg

248 ms

main-office.jpg

main-office.jpg

981 ms

print.css

print.css

247 ms

Accessibility Review

premiumhuis.com accessibility score

96

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

[id] attributes on active, focusable elements are not unique

Best Practices

premiumhuis.com 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

SEO Factors

premiumhuis.com SEO score

90

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

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 Premiumhuis.com 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 Premiumhuis.com 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

premiumhuis.com

Open Graph data is detected on the main page of Premium Huis. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: