Tools & Wizards About Us
mobile.whatrunswhere.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

mobile.whatrunswhere.com

WhatRunsWhere

Page Load Speed

3.3 sec in total

First Response

238 ms

Resources Loaded

2.9 sec

Page Rendered

179 ms

mobile.whatrunswhere.com screenshot

About Website

Click here to check amazing Mobile What Runs Where content for India. Otherwise, check out these important facts you probably never knew about mobile.whatrunswhere.com

Sign in to WhatRunsWhere - Industry leading display and mobile intelligence

Visit mobile.whatrunswhere.com

Key Findings

We analyzed Mobile.whatrunswhere.com page load time and found that the first response time was 238 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

mobile.whatrunswhere.com performance score

0

Network Requests Diagram

login.php

238 ms

css

68 ms

reset.min.css

39 ms

tabs.min.css

74 ms

base.min.css

132 ms

Our browser made a total of 38 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Mobile.whatrunswhere.com, 5% (2 requests) were made to Ssl.google-analytics.com and 5% (2 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (339 ms) relates to the external source Woopra.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 125.3 kB (41%)

Content Size

305.8 kB

After Optimization

180.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Mobile.whatrunswhere.com main page is 305.8 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. 25% of websites need less resources to load. Images take 118.6 kB which makes up the majority of the site volume.

HTML Optimization

-70%

Potential reduce by 23.6 kB

  • Original 33.8 kB
  • After minification 33.2 kB
  • After compression 10.1 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 23.6 kB or 70% of the original size.

Image Optimization

-23%

Potential reduce by 26.9 kB

  • Original 118.6 kB
  • After minification 91.7 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. Obviously, Mobile What Runs Where needs image optimization as it can save up to 26.9 kB or 23% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-35%

Potential reduce by 38.3 kB

  • Original 108.5 kB
  • After minification 106.2 kB
  • After compression 70.2 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 38.3 kB or 35% of the original size.

CSS Optimization

-81%

Potential reduce by 36.4 kB

  • Original 45.0 kB
  • After minification 42.2 kB
  • After compression 8.5 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. Mobile.whatrunswhere.com needs all CSS files to be minified and compressed as it can save up to 36.4 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 17 (50%)

Requests Now

34

After Optimization

17

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 34 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Mobile What Runs Where. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

login.php

login.php

238 ms

css

css

68 ms

reset.min.css

reset.min.css

39 ms

tabs.min.css

tabs.min.css

74 ms

base.min.css

base.min.css

132 ms

skeleton.min.css

skeleton.min.css

108 ms

layout.css

layout.css

107 ms

jquery.fancybox-1.3.4.css

jquery.fancybox-1.3.4.css

105 ms

jquery.min.js

jquery.min.js

82 ms

validate.min.js

validate.min.js

144 ms

tabs.min.js

tabs.min.js

107 ms

jquery.fancybox-1.3.4.pack.js

jquery.fancybox-1.3.4.pack.js

146 ms

jquery.placeholder.js

jquery.placeholder.js

148 ms

conversion.js

conversion.js

77 ms

w.js

w.js

144 ms

ga.js

ga.js

79 ms

659b8646-3948-423a-a5b5-896bd28b5b5f.js

659b8646-3948-423a-a5b5-896bd28b5b5f.js

245 ms

50aa6fd9703a780002000152.js

50aa6fd9703a780002000152.js

63 ms

99 ms

bg.jpg

bg.jpg

80 ms

signIn.gif

signIn.gif

42 ms

WhatRunsWhere.jpg

WhatRunsWhere.jpg

41 ms

secure.gif

secure.gif

41 ms

bg_light.jpg

bg_light.jpg

69 ms

twitter.gif

twitter.gif

66 ms

facebook.gif

facebook.gif

70 ms

linkedin.gif

linkedin.gif

71 ms

google.gif

google.gif

77 ms

divider.jpg

divider.jpg

78 ms

WRW.jpg

WRW.jpg

100 ms

s-BiyweUPV0v-yRb-cjciBsxEYwM7FgeyaSgU71cLG0.woff

s-BiyweUPV0v-yRb-cjciBsxEYwM7FgeyaSgU71cLG0.woff

87 ms

EFpQQyG9GqCrobXxL-KRMQFhaRv2pGgT5Kf0An0s4MM.woff

EFpQQyG9GqCrobXxL-KRMQFhaRv2pGgT5Kf0An0s4MM.woff

100 ms

__utm.gif

__utm.gif

19 ms

38 ms

339 ms

blank.gif

blank.gif

53 ms

help_left.png

help_left.png

32 ms

tagjs

tagjs

197 ms

SEO Factors

mobile.whatrunswhere.com SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mobile.whatrunswhere.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 Mobile.whatrunswhere.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.

Social Sharing Optimization

mobile.whatrunswhere.com

Open Graph description is not detected on the main page of Mobile What Runs Where. 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: