4.7 sec in total
258 ms
3.9 sec
522 ms
Click here to check amazing Phone House content for Netherlands. Otherwise, check out these important facts you probably never knew about phonehouse.nl
Bekijk op PhoneHouse.nl het grootste assortiment mobiele telefoons en goedkope gsm abonnementen van alle providers, nieuw en verlenging.
Visit phonehouse.nlWe analyzed Phonehouse.nl page load time and found that the first response time was 258 ms and then it took 4.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
phonehouse.nl performance score
name
value
score
weighting
Value3.8 s
27/100
10%
Value30.5 s
0/100
25%
Value28.2 s
0/100
10%
Value29,090 ms
0/100
30%
Value1
2/100
15%
Value44.6 s
0/100
10%
258 ms
638 ms
32 ms
983 ms
863 ms
Our browser made a total of 92 requests to load all elements on the main page. We found that 73% of them (67 requests) were addressed to the original Phonehouse.nl, 4% (4 requests) were made to Phonehouse.onlinetelecomservices.nl and 3% (3 requests) were made to D3c3cq33003psk.cloudfront.net. The less responsive or slowest element that took the longest time to load (983 ms) relates to the external source Typhone.nl.
Page size can be reduced by 2.8 MB (47%)
6.0 MB
3.2 MB
In fact, the total size of Phonehouse.nl main page is 6.0 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 2.6 MB which makes up the majority of the site volume.
Potential reduce by 85.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 85.8 kB or 85% of the original size.
Potential reduce by 174.8 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. Phone House images are well optimized though.
Potential reduce by 1.6 MB
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 1.6 MB or 74% of the original size.
Potential reduce by 896.9 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. Phonehouse.nl needs all CSS files to be minified and compressed as it can save up to 896.9 kB or 87% of the original size.
Number of requests can be reduced by 54 (62%)
87
33
The browser has sent 87 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Phone House. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 42 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
phonehouse.nl
258 ms
www.phonehouse.nl
638 ms
j.php
32 ms
huawei-mate-8$03ba7070-7f29-4b65-8117-14f770b5d8c4-groot.png
983 ms
sony-xperia-z5-compact-black$35f101f9-3137-4a9d-a71f-d563bd864dcb-groot.png
863 ms
jquery-2.1.3.min.js
8 ms
require.js
94 ms
main.js
177 ms
samsung-s7-gearvr-actie.png
411 ms
samsung-s7-bannerx2.png
506 ms
samsung-s7-smallx2.png
494 ms
beste-winkelketen.png
187 ms
beste-webshop.png
179 ms
v.gif
24 ms
style.css
115 ms
ui.js
115 ms
modal.js
115 ms
form.js
170 ms
log.js
169 ms
mediaqueries.js
182 ms
vector.js
250 ms
foundation.equalizer.js
248 ms
cart.js
271 ms
cart.js
304 ms
widgets.js
7 ms
analytics.js
325 ms
usabilla.js
327 ms
ui.js
357 ms
layerslider.js
382 ms
opentag-56044-424641.js
30 ms
modernizr.js
384 ms
fastclick.js
446 ms
jquery.onloader.min.js
444 ms
20 ms
analytics.js
22 ms
style-blessed2.css
347 ms
style-blessed1.css
444 ms
39 ms
location.js
360 ms
readmore.min.js
364 ms
jquery.placeholder.js
369 ms
jquery.unveil.min.js
378 ms
jquery.touchSwipe.min.js
393 ms
jquery.nicescroll.min.js
546 ms
jquery.scrollUp.min.js
542 ms
jquery.cookie.js
542 ms
collect
15 ms
widget.min.js
506 ms
jquery.serializeObject.min.js
498 ms
greensock.js
299 ms
layerslider.transitions.js
299 ms
foundation.min.js
194 ms
phonehouse-logo.svg
88 ms
awards-header.png
86 ms
number-transfer.svg
85 ms
store.svg
96 ms
pickup.svg
117 ms
clock.svg
111 ms
vodafone.oncolor.svg
778 ms
ben.oncolor.svg
166 ms
prolongation-white-bottom.svg
169 ms
kpn.oncolor.svg
787 ms
small.tmobile.oncolor.svg
192 ms
tele2.oncolor.svg
206 ms
simcard.svg
249 ms
telfort.svg
251 ms
cpwtrade.ttf
231 ms
icomoon.svg
268 ms
jquery.selectBoxIt.min.js
321 ms
layerslider.kreaturamedia.jquery.js
294 ms
samsung-galaxy-s6-32gb-black$c893832e-a1f8-4f4c-a4b2-818d6129c48b-groot.png
255 ms
skin.css
95 ms
huawei-p8-grey$a499c814-05b2-4e4b-8174-65f2eafacc19-groot.png
664 ms
apple-iphone-5s-16gb$39303e4a-3e4c-461e-a95f-60bb3119a5d1-groot.png
665 ms
06ac546a5b6b.js
38 ms
tag2
231 ms
vodafone.svg
577 ms
blank.gif
84 ms
kpn.svg
491 ms
skin.png
199 ms
blank.gif
83 ms
vodafone.svg
277 ms
vodafone.oncolor.svg
418 ms
typhone_desktop_alternative_right.png
100 ms
PostData.js
96 ms
consent-widget-1.1.0.min.js
96 ms
event.php
147 ms
sp_2.0.2.js
93 ms
collect
99 ms
s
125 ms
i
37 ms
fbx_nosync.php
37 ms
phonehouse.nl accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
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.
phonehouse.nl best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
phonehouse.nl SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
Document uses legible font sizes
Tap targets are not sized appropriately
NL
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Phonehouse.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 Phonehouse.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.
phonehouse.nl
Open Graph description is not detected on the main page of Phone House. 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: