2.3 sec in total
259 ms
1.6 sec
489 ms
Click here to check amazing Percentmobile content. Otherwise, check out these important facts you probably never knew about percentmobile.com
Mobile Analytics, Simplified. A Mobile Analytics Blog by PercentMobile.
Visit percentmobile.comWe analyzed Percentmobile.com page load time and found that the first response time was 259 ms and then it took 2.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
percentmobile.com performance score
name
value
score
weighting
Value2.4 s
72/100
10%
Value2.4 s
92/100
25%
Value2.4 s
98/100
10%
Value210 ms
89/100
30%
Value0
100/100
15%
Value2.7 s
97/100
10%
259 ms
27 ms
32 ms
24 ms
15 ms
Our browser made a total of 66 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Percentmobile.com, 12% (8 requests) were made to Assets.tumblr.com and 11% (7 requests) were made to About.delivr.com. The less responsive or slowest element that took the longest time to load (437 ms) relates to the external source Disqus.com.
Page size can be reduced by 1.0 MB (58%)
1.8 MB
762.1 kB
In fact, the total size of Percentmobile.com main page is 1.8 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. Javascripts take 1.0 MB which makes up the majority of the site volume.
Potential reduce by 348.3 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 348.3 kB or 72% of the original size.
Potential reduce by 4.1 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. Percentmobile images are well optimized though.
Potential reduce by 589.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 589.3 kB or 59% of the original size.
Potential reduce by 102.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. Percentmobile.com needs all CSS files to be minified and compressed as it can save up to 102.9 kB or 73% of the original size.
Number of requests can be reduced by 44 (70%)
63
19
The browser has sent 63 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Percentmobile. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 27 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
mobileanalyticssimplified.com
259 ms
pre_tumblelog.js
27 ms
tumblelog_post_message_queue.js
32 ms
stylesheet.css
24 ms
addthis_widget.js
15 ms
element.js
192 ms
index.js
191 ms
header_iframe
163 ms
b_logo_service_share_16_16.gif
134 ms
readwriteweb
112 ms
tumblr_lmqmflMNCU1qzz69qo1_500.png
101 ms
7603131
307 ms
get_num_replies.js
437 ms
default.pm
30 ms
DHTMLSubMenu.gz.js
21 ms
embed-min.css
8 ms
video-min.css
14 ms
json-min.js
16 ms
embed-min.js
17 ms
mask.png
12 ms
alert.png
12 ms
thumbnail
48 ms
nav_tab_active.png
8 ms
delivr-logo-retina-print-350-76.png
42 ms
nav_tab_default.png
42 ms
combined_jquery.js
56 ms
global.js
66 ms
combined_li_tracking.js
45 ms
font-awesome.css
43 ms
combined_presentation.css
74 ms
combined_player_presentation.js
82 ms
combined_old_embed.js
76 ms
ga.js
107 ms
beacon.js
98 ms
beyond-the-mobile-web-by-yiibu-1-728.jpg
282 ms
7603131
74 ms
lead-form
254 ms
1x1.gif
43 ms
logo_embed_20x20_v1.png
43 ms
fontawesome-webfont.woff
61 ms
icons.svg
36 ms
translateelement.css
61 ms
main.js
185 ms
footer_iframe
35 ms
__utm.gif
24 ms
__utm.gif
19 ms
analytics.html
142 ms
impixu
229 ms
boost
81 ms
300lo.json
165 ms
impixu
123 ms
login_check.html
50 ms
sh.07f0d9bf220d07a763adad1e.html
43 ms
element_main.js
109 ms
rapid-3.36.js
131 ms
rapidworker-1.2.js
129 ms
iframe_logo.png
65 ms
avatar_acd2a5ca7b1a_40.png
48 ms
translate_24dp.png
80 ms
l
44 ms
googlelogo_color_42x16dp.png
82 ms
ga.js
101 ms
analytics.js
89 ms
cs.js
39 ms
__utm.gif
15 ms
cedexis.radar.js
4 ms
percentmobile.com accessibility score
percentmobile.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
percentmobile.com SEO score
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 Percentmobile.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 Percentmobile.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.
percentmobile.com
Open Graph description is not detected on the main page of Percentmobile. 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: