7.7 sec in total
1.5 sec
5.6 sec
596 ms
Click here to check amazing Interhome content for Netherlands. Otherwise, check out these important facts you probably never knew about interhome.nl
Vind uw ideale vakantiewoning bij Interhome. Kies uit circa 40.000 gecontroleerde vakantiewoningen in 28 landen.
Visit interhome.nlWe analyzed Interhome.nl page load time and found that the first response time was 1.5 sec and then it took 6.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
interhome.nl performance score
name
value
score
weighting
Value3.3 s
41/100
10%
Value6.6 s
8/100
25%
Value5.4 s
56/100
10%
Value1,610 ms
12/100
30%
Value0
100/100
15%
Value10.8 s
22/100
10%
1509 ms
78 ms
427 ms
2902 ms
730 ms
Our browser made a total of 117 requests to load all elements on the main page. We found that 31% of them (36 requests) were addressed to the original Interhome.nl, 28% (33 requests) were made to Static.xx.fbcdn.net and 20% (23 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (2.9 sec) belongs to the original domain Interhome.nl.
Page size can be reduced by 309.7 kB (23%)
1.3 MB
1.0 MB
In fact, the total size of Interhome.nl main page is 1.3 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 941.9 kB which makes up the majority of the site volume.
Potential reduce by 94.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 25.5 kB, which is 22% 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 94.6 kB or 82% of the original size.
Potential reduce by 59.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. Interhome images are well optimized though.
Potential reduce by 155.6 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 155.6 kB or 58% of the original size.
Number of requests can be reduced by 49 (44%)
112
63
The browser has sent 112 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Interhome. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 31 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
www.interhome.nl
1509 ms
409852029.js
78 ms
css.ashx
427 ms
js.ashx
2902 ms
pool.jpg
730 ms
visual_slider_ES_1020x600.jpg
2469 ms
city.jpg
2476 ms
berge-summer-AT.jpg
882 ms
winter-ski.jpg
2663 ms
logojpg.jpg
754 ms
USP_Specialist_33x33.png
897 ms
USP_Local_33x33.png
981 ms
USP_Hotline_33x33.png
995 ms
white_small.gif
1194 ms
USP_Specialist.gif
1175 ms
USP_Quality.gif
1909 ms
USP_Secure.gif
1908 ms
USP_Local.gif
2462 ms
logo-visa.png
2464 ms
logo-mastercard.png
2471 ms
NL-iDEAL.jpg
2463 ms
logo-digicert-footer.png
2918 ms
NL-calamiteitenfond-sgr-anvr1.gif
2469 ms
logo-migros.png
2471 ms
gtm.js
147 ms
noise.png
2393 ms
arrow.png
2495 ms
powered-by-interhome.png
2393 ms
powered-by-google-on-white.png
2394 ms
icon.png
2490 ms
faceted-search.png
2406 ms
footer.png
2569 ms
likebox.php
543 ms
likebox.php
282 ms
cb2f7531-f3b7-4f58-afb9-2a698424299f.js
300 ms
conversion_async.js
64 ms
analytics.js
84 ms
iMAWebCookie.js
325 ms
ld.js
191 ms
fbevents.js
186 ms
bat.js
34 ms
272 ms
359 ms
collect
73 ms
collect
331 ms
collect
64 ms
collect
331 ms
MHCDtc1Nm3F.css
463 ms
7WdtcX-OyrO.css
533 ms
XnpJYbMmua9.css
615 ms
kpvb6wHo6R4.css
552 ms
Bo82YMAVvEK.css
579 ms
e9DQ5gFtxxa.css
666 ms
mm0vjjrXdxr.js
758 ms
Ta5YnQdNSFy.js
895 ms
XXn49zk5GnD.js
659 ms
OwNnuMlrnxQ.js
739 ms
9vSWWzdE5eF.js
1023 ms
7ztEcde0Vs0.js
961 ms
n2oJSueYiMi.js
753 ms
XOfKJ6pUv0L.js
987 ms
rRqMEKuYkwU.js
959 ms
EEE2zYcQ4va.js
986 ms
Zp2gfEhcpC8.js
987 ms
d2Tdc2D6-_o.js
1283 ms
X6hCdNrzbmL.js
988 ms
tsktgDt3YVI.js
988 ms
NZ1ljYgAVg4.js
985 ms
299 ms
111 ms
blank.gif
122 ms
event
68 ms
g2xrZc_4hOn.css
1032 ms
ofcqdwKirzc.css
1246 ms
KFBLdp-a6q1.js
1223 ms
Xz4mBupxTkn.js
1221 ms
313 ms
ga-audiences
364 ms
event
227 ms
SnapEngage_Button_Final_nl.png
2004 ms
1374878_10151729593181020_382929826_n.png
991 ms
1654122_10152570578741020_3378133163581402856_n.jpg
949 ms
12241470_773914136065453_1409032000299321269_n.jpg
942 ms
12705166_879951058770271_433914901623022131_n.jpg
937 ms
11811470_722283927901472_8781574974923170242_n.jpg
937 ms
10885094_800058026721777_3818972823149185389_n.jpg
934 ms
12279109_792400510870229_2996294521180984507_n.jpg
1000 ms
12391357_916985641725773_8390757792006365477_n.jpg
1003 ms
12654323_142908509426473_2832074546756963705_n.jpg
1003 ms
HEyyDkPknAC.png
579 ms
wL6VQj7Ab77.png
580 ms
s7jcwEQH7Sx.png
582 ms
1374878_10151729593181020_382929826_n.png
1009 ms
12745626_10153245714931020_2901283559513670128_n.jpg
824 ms
12661789_10153225958346020_4800437178374417792_n.jpg
821 ms
12645145_10153225958336020_5775343883150971836_n.jpg
821 ms
12651209_10153225958331020_1130090849979736384_n.jpg
824 ms
12687826_10153225895841020_1988415038183393317_n.jpg
823 ms
12650894_10153225895861020_3604673064790438653_n.jpg
1003 ms
12654212_10153225895856020_7409681946842554871_n.jpg
1002 ms
12654674_10153225858946020_361132432528979420_n.jpg
1001 ms
12644803_10153225858951020_6412672889725044161_n.jpg
1002 ms
12650889_10153225858941020_8913373797882764744_n.jpg
1001 ms
12631506_10153225840496020_3653682621209379268_n.jpg
1002 ms
12646993_10153225840486020_5312185956036032310_n.jpg
1003 ms
12651090_10153225840491020_5259605972176060248_n.jpg
1004 ms
KoALExrj-T2.png
508 ms
67g7JcLdRXw.png
509 ms
kpVuqazI0LW.png
200 ms
CookieWarning.ashx
324 ms
slides.min.jquery.js
156 ms
FacetedSearch.ashx
286 ms
select2.png
102 ms
pagination.png
96 ms
wBg80dBy2Ra.js
69 ms
WIQcBxwlOXr.js
245 ms
dis.aspx
205 ms
interhome.nl accessibility score
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
[aria-*] attributes do not match their roles
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
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
Image elements do not have [alt] attributes
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
interhome.nl best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
interhome.nl SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
NL
NL
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Interhome.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 Interhome.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.
interhome.nl
Open Graph data is detected on the main page of Interhome. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: