5.7 sec in total
302 ms
4 sec
1.4 sec
Visit whatmobile.net now to see the best up-to-date What Mobile content for Pakistan and also check out these interesting facts you probably never knew about whatmobile.net
Home
Visit whatmobile.netWe analyzed Whatmobile.net page load time and found that the first response time was 302 ms and then it took 5.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
whatmobile.net performance score
name
value
score
weighting
Value4.4 s
16/100
10%
Value25.8 s
0/100
25%
Value6.0 s
46/100
10%
Value160 ms
94/100
30%
Value0.085
93/100
15%
Value7.5 s
47/100
10%
302 ms
28 ms
234 ms
320 ms
160 ms
Our browser made a total of 121 requests to load all elements on the main page. We found that 50% of them (61 requests) were addressed to the original Whatmobile.net, 9% (11 requests) were made to Openx.datacareltd.net and 6% (7 requests) were made to W.soundcloud.com. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Whatmobile.net.
Page size can be reduced by 956.2 kB (8%)
12.4 MB
11.5 MB
In fact, the total size of Whatmobile.net main page is 12.4 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. 60% of websites need less resources to load. Images take 11.1 MB which makes up the majority of the site volume.
Potential reduce by 65.0 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 65.0 kB or 79% of the original size.
Potential reduce by 126.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. What Mobile images are well optimized though.
Potential reduce by 291.3 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 291.3 kB or 65% of the original size.
Potential reduce by 473.2 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. Whatmobile.net needs all CSS files to be minified and compressed as it can save up to 473.2 kB or 63% of the original size.
Number of requests can be reduced by 59 (50%)
117
58
The browser has sent 117 CSS, Javascripts, AJAX and image requests in order to completely render the main page of What Mobile. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and from 18 to 1 for CSS and as a result speed up the page load time.
www.whatmobile.net
302 ms
ga.js
28 ms
wp-emoji-release.min.js
234 ms
dashicons.min.css
320 ms
thickbox.css
160 ms
style.css
313 ms
advps-style.css
162 ms
styles.css
161 ms
frontend.css
320 ms
style.css
631 ms
flexslider.css
396 ms
jetpack.css
545 ms
addtoany.min.css
469 ms
wpcufpn_front.css
469 ms
css
33 ms
jquery.min.js
34 ms
flags.js
469 ms
advps.frnt.script.js
552 ms
jquery.bxslider.min.js
705 ms
jquery.fitvids.min.js
625 ms
frontend.min.js
624 ms
modernizr.custom.min.js
706 ms
css
34 ms
css
43 ms
show_ads.js
6 ms
__utm.gif
10 ms
analytics.js
13 ms
collect
87 ms
VfiPxiD.jpg
32 ms
mpd-mpu.gif
413 ms
WM-LOGO-WEB-2_cent.png
167 ms
autodesk.jpg
875 ms
what-mobile-results.jpg
411 ms
DSC_1030.jpg
1761 ms
reactions-image-en_us.png
247 ms
DSC_0060.jpg
1223 ms
DSC_0050.jpg
1356 ms
alcatel.jpg
1561 ms
DSC_0653-350x200.jpg
571 ms
h7-back1-350x200.jpg
764 ms
DSC_0001-350x200.jpg
943 ms
LOZTriForceHeroes_artwork-350x200.jpg
1167 ms
dynast-warriors-8-350x200.jpg
1222 ms
DSC_0487-new-350x200.jpg
1359 ms
galaxy-tab-s2-350x200.jpg
1397 ms
20462365406_23b9e7447e_k-350x200.jpg
1400 ms
Cyber_Monday_logo_800w_600h-350x200.jpg
1587 ms
sh_hacker-in-hoodie1500px-350x200.jpg
1592 ms
better-nexus-pics-350x200.jpg
1555 ms
xl-2015-android-marshmallow-1-350x200.jpg
1562 ms
Chromecast-1-smaller-350x200.png
1867 ms
Meizu-Niux-Leak-2-350x200.jpg
1792 ms
apple-take-350x200.jpg
1794 ms
5thAveHero-cut-350x200.png
1979 ms
facebook-new2.png
1747 ms
twitter-new2.png
1903 ms
instagram-new2.png
1912 ms
youtube-new2.png
1947 ms
linkedin-new2.png
1949 ms
flickr-new2.png
2022 ms
vimeo-new2.png
2060 ms
rss-new2.png
2068 ms
M9_3V_Gold_010315_EMEA-600x3501-90x90.png
2106 ms
iRig-UA-90x90.jpg
2104 ms
HTC-One-M81-90x90.jpg
2133 ms
ajs.php
242 ms
Samsung-Galaxy-S6-edge-90x90.jpg
2174 ms
e06d92cd6705c42d60cec7a3259e52f6.jpg
170 ms
lg.php
193 ms
mob-dropdown.png
1966 ms
ajs.php
199 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
28 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
38 ms
1b9e1602d5f5b4ce724bada377bf2e56.png
245 ms
lg.php
121 ms
ajs.php
127 ms
172 ms
to-top-arrow.png
1608 ms
search-40x40.png
1647 ms
review-star-box-sprite90x90.png
1646 ms
2d687e43de3661f8e89a95405a369a71.gif
170 ms
lg.php
141 ms
widgets.js
6 ms
sdk.js
270 ms
ca-pub-6605946721097912.js
107 ms
zrt_lookup.html
36 ms
show_ads_impl.js
51 ms
aci.js
185 ms
ajs.php
136 ms
ads
410 ms
osd.js
6 ms
interstate-0ab59479718c8235122cad6b16a66953d725c43a.css
241 ms
widget-ea7fb002.css
65 ms
widget-4cab6819.js
191 ms
timeline.1b43d11859b7663a2225b885f87704a5.js
23 ms
playicon.png
1441 ms
lg.php
107 ms
92 ms
197 ms
loadicon_b.gif
1465 ms
syndication
97 ms
606385652985380864
182 ms
156 ms
xd_arbiter.php
269 ms
xd_arbiter.php
435 ms
logo-200x120-177df3dd.png
34 ms
250 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
10 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
8 ms
ga.js
88 ms
multi-sounds-3fc9613a.js
84 ms
error-698b3c1d.js
55 ms
3c70QYZk_normal.jpeg
183 ms
4E5KUoA0_normal.jpg
208 ms
beacon.js
101 ms
pageview
375 ms
logo_grey-377f1b9e.png
70 ms
__utm.gif
26 ms
__utm.gif
28 ms
match
187 ms
jot
31 ms
whatmobile.net accessibility score
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
Image elements do not have [alt] attributes
Links do not have a discernible name
whatmobile.net 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
whatmobile.net 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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Whatmobile.net 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 Whatmobile.net 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.
whatmobile.net
Open Graph description is not detected on the main page of What Mobile. 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: