3.7 sec in total
172 ms
3.2 sec
366 ms
Visit fonehouse.co.uk now to see the best up-to-date Fonehouse content for United Kingdom and also check out these interesting facts you probably never knew about fonehouse.co.uk
Get the latest and greatest mobile phone deals & contracts at Fonehouse, all with FREE next day delivery! Best prices guaranteed! All the major networks and big brands such as Apple iPhone, Samsung an...
Visit fonehouse.co.ukWe analyzed Fonehouse.co.uk page load time and found that the first response time was 172 ms and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
fonehouse.co.uk performance score
name
value
score
weighting
Value3.1 s
45/100
10%
Value11.2 s
0/100
25%
Value6.4 s
41/100
10%
Value1,530 ms
13/100
30%
Value0.264
46/100
15%
Value10.6 s
23/100
10%
172 ms
935 ms
585 ms
490 ms
246 ms
Our browser made a total of 161 requests to load all elements on the main page. We found that 73% of them (118 requests) were addressed to the original Fonehouse.co.uk, 7% (11 requests) were made to Mark.reevoo.com and 3% (5 requests) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (935 ms) belongs to the original domain Fonehouse.co.uk.
Page size can be reduced by 1.7 MB (42%)
4.1 MB
2.4 MB
In fact, the total size of Fonehouse.co.uk main page is 4.1 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. 65% of websites need less resources to load. Images take 2.2 MB which makes up the majority of the site volume.
Potential reduce by 225.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 64.5 kB, which is 25% 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 225.6 kB or 87% of the original size.
Potential reduce by 230.3 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. Fonehouse images are well optimized though.
Potential reduce by 692.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 692.7 kB or 72% of the original size.
Potential reduce by 581.1 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. Fonehouse.co.uk needs all CSS files to be minified and compressed as it can save up to 581.1 kB or 84% of the original size.
Number of requests can be reduced by 45 (29%)
155
110
The browser has sent 155 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fonehouse. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 36 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
fonehouse.co.uk
172 ms
www.fonehouse.co.uk
935 ms
GetResource.ashx
585 ms
GetResource.ashx
490 ms
GetResource.ashx
246 ms
GetResource.ashx
176 ms
GetResource.ashx
176 ms
WebResource.axd
185 ms
ScriptResource.axd
348 ms
ScriptResource.axd
250 ms
PortalTemplate.aspx
247 ms
jquery.1.5.1.min.js
445 ms
jquery-1.7.1.js
409 ms
cookie-consent.js
330 ms
jquery.min.js
26 ms
Skin.css
394 ms
6224.js
54 ms
slides.min.jquery.js
349 ms
jquery.min.js
9 ms
jquery.min.js
38 ms
jquery.easing.1.3.js
362 ms
jquery.contentcarousel.js
408 ms
icons-core-ie7.css
83 ms
serach_icon.png
82 ms
fonehouse.png
83 ms
free_delivery.png
84 ms
upgrade.png
85 ms
enter_compition.png
85 ms
fonehouse-as-seen-on-BBC.png
86 ms
EE.png
162 ms
virgin.png
162 ms
home_icon.png
164 ms
home_icon_resp.png
164 ms
Galaxy-S7-32GB.aspx
259 ms
Galaxy-S7-edge-32GB.aspx
262 ms
Sale.aspx
485 ms
LG-G4C.aspx
333 ms
HTC-Desire-510.aspx
434 ms
Microsoft-Lumia.aspx
420 ms
iPhone-6s.aspx
506 ms
EE-Sim-Only.aspx
616 ms
iphone-6S_spacegray145X255.aspx
417 ms
1.png
501 ms
iphone-6sPlusSilver145x255.aspx
503 ms
iPhone-6_SpaceGray_145x256.aspx
516 ms
SonyXperiaZ5black145front.aspx
567 ms
iPhone-6-Plus_SpaceGray_145x256.aspx
585 ms
galaxys6edgeplus_black_145x256.aspx
590 ms
galaxys6edgeplus_black_145x256.aspx
588 ms
galaxy7_145x255.aspx
599 ms
Galaxy-S7-edge_black_front_145x256.aspx
651 ms
galaxys6_black_front_145x255.aspx
666 ms
iphone-6s_spaceGray145x255.aspx
671 ms
iphone6sSilver145x255.aspx
674 ms
iphone-6s_SpaceGray145x255.aspx
683 ms
iphone6s_Silver145x255.aspx
697 ms
Galaxy-S5_black_front_145x256.aspx
733 ms
Lumia-650_black_front_145_256.aspx
752 ms
Microsoft-Lumia-640_black_145x255.aspx
743 ms
HomepageSlider.css
684 ms
Samsung-Galaxy-J5_145x256_black_front.aspx
694 ms
lg-g4-gray_145x255.aspx
711 ms
sony-xperia-c4-black_front_145x256.aspx
741 ms
SonyXperiaZ5compactblack145256front.aspx
768 ms
galaxys6edge_front_black_145x255.aspx
768 ms
Nokia-Lumia-435_145x256_black_front.aspx
806 ms
Samsung-Note-4_black_145x255.aspx
805 ms
Samsung_Galaxy_s5_Mini_black_front_145.aspx
805 ms
Microsoft-Lumia-950_front_black_145x256.aspx
809 ms
Microsoft-Lumia-950XL_front_black_145x256.aspx
716 ms
Samsung-Galaxy-A3_black_front_145x25.aspx
722 ms
iPhone-5s_Silver_145x256.aspx
651 ms
Samsung-Galaxy-A5_black_front_145x255.aspx
568 ms
HTC-Desire-820_front_gray_145x255.aspx
567 ms
iPhone-6_SpaceGray_145x256.aspx
616 ms
HTC-Desire-626_blue_front_145x256.aspx
565 ms
galaxys6_black_front_145x255.aspx
546 ms
iPhone-6_SpaceGray_145x256.aspx
544 ms
iPhone-6-Plus_SpaceGray_145x256.aspx
542 ms
galaxys6edge_front_black_145x255.aspx
533 ms
Nokia_635_white_front_145x256.aspx
576 ms
Sony-Xperia-M4-Aqua_black_145x255.aspx
559 ms
HTC-Desire-620_front_gray_145x255.aspx
559 ms
lgg4c145256_whitefront.aspx
556 ms
motorola_moto_g_black_front_85x150.aspx
547 ms
Motorola-Moto-E_black_85x150.aspx
529 ms
Sony-Xperia-E3_black_front_85x150.aspx
579 ms
HTC-Desire-510_gray_85x150.aspx
564 ms
LGG3_black_145x255.aspx
561 ms
sub_banner.jpg
568 ms
sub_banner_mobileview.png
558 ms
white_clr.aspx
544 ms
black_clr.aspx
565 ms
Coral.aspx
549 ms
grey.aspx
542 ms
silver.aspx
547 ms
gold.aspx
532 ms
space-gray.aspx
498 ms
bbcbanner.jpg
564 ms
reevoo_mark.js
135 ms
iphone6s.jpg
547 ms
ga.js
102 ms
tag.js
163 ms
455239.js
335 ms
jquery-ui.css
65 ms
cookie-consent.css
79 ms
winipadstore.jpg
443 ms
visa.png
442 ms
master.png
442 ms
reevoo_mark.js
129 ms
amex.png
441 ms
like.php
247 ms
jcb.png
541 ms
facebook.png
533 ms
twitter.png
534 ms
cookie-consent.css
489 ms
gplus.png
531 ms
youtube.png
531 ms
9330.js
110 ms
tag.js
75 ms
57 ms
__utm.gif
25 ms
linkedin.png
488 ms
vecapture.js
124 ms
jquery.min.js
28 ms
blog.png
509 ms
phone_icon.png
512 ms
shoping_cart_icon.png
532 ms
left_arow.png
526 ms
rgth_arow.png
527 ms
collect
67 ms
box_hover_bg.png
519 ms
.jsonp
46 ms
white-opacity-30.png
27 ms
FNH.json
129 ms
ga-audiences
47 ms
storage.min.html
90 ms
7392275
45 ms
zones
42 ms
centre-c_s1.png
497 ms
Galaxy-S7-32GB.aspx
510 ms
loading.gif
515 ms
slider_pag_active.png
513 ms
slider_pag_icon.png
512 ms
dropdown.png
512 ms
7392275
37 ms
vpc6VNjRPXV.js
313 ms
LVx-xkvaJ0b.png
321 ms
reevoomark-b8c3a9ce64633822b4b284a4023e740e.css
16 ms
ui-bg_diagonal-maze_20_6e4f1c_10x10.png
29 ms
ui-bg_fine-grain_10_eceadf_60x60.png
28 ms
product_summary
11 ms
product_summary
11 ms
product_summary
12 ms
product_summary
11 ms
product_summary
11 ms
product_summary
11 ms
product_summary
11 ms
product_summary
11 ms
product_summary
11 ms
product_summary
12 ms
fonehouse.co.uk 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
[role]s do not have all required [aria-*] attributes
[aria-*] attributes do not have valid values
ARIA IDs are not unique
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
Buttons do not have an accessible name
Form elements do not have associated labels
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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.
fonehouse.co.uk best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
fonehouse.co.uk 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 doesn't use legible font sizes
Tap targets are not sized appropriately
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fonehouse.co.uk can be misinterpreted by Google and other search engines. Our service has detected that English 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 Fonehouse.co.uk 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.
fonehouse.co.uk
Open Graph description is not detected on the main page of Fonehouse. 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: