4.7 sec in total
192 ms
4.3 sec
160 ms
Welcome to classic.118.com homepage info - get ready to check Classic 118 best content right away, or after learning these important things about classic.118.com
118118.com comprehensive business search connects you to UK's local business, providing all the information from the business directory : addresses and telephone numbers
Visit classic.118.comWe analyzed Classic.118.com page load time and found that the first response time was 192 ms and then it took 4.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
classic.118.com performance score
192 ms
537 ms
5 ms
9 ms
9 ms
Our browser made a total of 88 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Classic.118.com, 19% (17 requests) were made to 118118.com and 9% (8 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (2.6 sec) relates to the external source Rum-collector.pingdom.net.
Page size can be reduced by 572.9 kB (59%)
963.9 kB
391.0 kB
In fact, the total size of Classic.118.com main page is 963.9 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. Javascripts take 665.4 kB which makes up the majority of the site volume.
Potential reduce by 120.7 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 120.7 kB or 75% of the original size.
Potential reduce by 1.6 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. Classic 118 images are well optimized though.
Potential reduce by 398.8 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 398.8 kB or 60% of the original size.
Potential reduce by 51.7 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. Classic.118.com needs all CSS files to be minified and compressed as it can save up to 51.7 kB or 79% of the original size.
Number of requests can be reduced by 52 (65%)
80
28
The browser has sent 80 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Classic 118. 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 4 to 1 for CSS and as a result speed up the page load time.
classic.118.com
192 ms
www.118118.com
537 ms
gen_landing.css
5 ms
gen_homepage.css
9 ms
locale_118_en_gb.css
9 ms
gen_modernizer.js
10 ms
jquery.min.js
32 ms
gen_landing_footer.js
27 ms
prum.min.js
7 ms
gpt.js
5 ms
pubads_impl_81.js
6 ms
container.html
35 ms
logo_landing_stripe_118.png
54 ms
ads
70 ms
118218_footer_ad_facebook.png
253 ms
118_footer_tv_icon.jpg
296 ms
118_footer_lists_icon.png
294 ms
118218_footer_ad_twitter.png
252 ms
logo_landing_118.png
17 ms
email_loader.gif
17 ms
museosans-500-webfont.woff
232 ms
museosans-900-webfont.woff
236 ms
dfp_left
224 ms
ajs.php
270 ms
osd.js
5 ms
PinExt.png
17 ms
962082_p_508011ee27ae5.jpg
136 ms
popout.png
4 ms
adsbygoogle.js
9 ms
lg.php
36 ms
flag_sprite_sm.png
27 ms
ca-pub-3765026033936536.js
33 ms
zrt_lookup.html
32 ms
show_ads_impl.js
69 ms
analytics.js
26 ms
loader0.js
72 ms
_Incapsula_Resource
15 ms
match.aspx
54 ms
_Incapsula_Resource
45 ms
collect
38 ms
ads
268 ms
collect
65 ms
7860-901-10-9522.js
39 ms
c
202 ms
ga-audiences
38 ms
activeview
12 ms
m_js_controller.js
21 ms
abg.js
42 ms
favicon
74 ms
googlelogo_color_112x36dp.png
71 ms
nessie_icon_thin_arrow_big_white.png
24 ms
s
38 ms
x_button_blue2.png
24 ms
application2.js
126 ms
ui
30 ms
MdyApZkAHG2-UELdOwjNjjFZXSz-CGj4o1JtDR7aGgs.js
4 ms
beacon.gif
2586 ms
plusone.js
143 ms
all.js
81 ms
widgets.js
4 ms
pinit.js
22 ms
button.831500944bc3eb7ea5276ccdc3f71d2e.js
18 ms
pinit_main.js
41 ms
tweet_button.6a78875565a912489e9aef879c881358.en.html
17 ms
59 ms
cb=gapi.loaded_0
23 ms
cb=gapi.loaded_1
41 ms
fastbutton
170 ms
xd_arbiter.php
70 ms
xd_arbiter.php
138 ms
ping
63 ms
storage.html
151 ms
postmessageRelay
63 ms
like.php
91 ms
jot
117 ms
api.js
58 ms
core:rpc:shindig.random:shindig.sha1.js
110 ms
2536007149-postmessagerelay.js
104 ms
vpc6VNjRPXV.js
177 ms
LVx-xkvaJ0b.png
171 ms
cb=gapi.loaded_0
35 ms
cb=gapi.loaded_1
34 ms
storage.js
29 ms
visits
320 ms
8268dd8318fdd31deede802e22e0904e.css
35 ms
st-paddys.png
27 ms
activeview
14 ms
activeview
14 ms
classic.118.com SEO score
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Classic.118.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Classic.118.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.
classic.118.com
Open Graph description is not detected on the main page of Classic 118. 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: