Tools & Wizards About Us
whatrunswhere.com screenshot

Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 64

    Accessibility

    Visual factors better than
    that of 29% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 74

    SEO

    Google-friendlier than
    31% of websites

whatrunswhere.com

Pathmatics - Ad Intelligence for the Digital Landscape

Page Load Speed

2 sec in total

First Response

70 ms

Resources Loaded

1.7 sec

Page Rendered

280 ms

whatrunswhere.com screenshot

About Website

Visit whatrunswhere.com now to see the best up-to-date Whatrunswhere content for India and also check out these interesting facts you probably never knew about whatrunswhere.com

Pathmatics empowers brands with the digital marketing intelligence they need to seize new opportunities on digital and drive the next phase of business growth

Visit whatrunswhere.com

Key Findings

We analyzed Whatrunswhere.com page load time and found that the first response time was 70 ms and then it took 2 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.

Performance Metrics

whatrunswhere.com performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.4 s

6/100

10%

LCP (Largest Contentful Paint)

Value7.1 s

5/100

25%

SI (Speed Index)

Value13.2 s

2/100

10%

TBT (Total Blocking Time)

Value12,940 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.056

98/100

15%

TTI (Time to Interactive)

Value23.9 s

1/100

10%

Network Requests Diagram

whatrunswhere.com

70 ms

www.whatrunswhere.com

67 ms

www.whatrunswhere.com

199 ms

css

64 ms

reset.min.css

31 ms

Our browser made a total of 68 requests to load all elements on the main page. We found that 49% of them (33 requests) were addressed to the original Whatrunswhere.com, 6% (4 requests) were made to Fonts.gstatic.com and 4% (3 requests) were made to Pixel.prfct.co. The less responsive or slowest element that took the longest time to load (338 ms) relates to the external source Pixel.rubiconproject.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 506.3 kB (42%)

Content Size

1.2 MB

After Optimization

708.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-70%

Potential reduce by 27.4 kB

  • Original 39.3 kB
  • After minification 38.3 kB
  • After compression 12.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 27.4 kB or 70% of the original size.

Image Optimization

-9%

Potential reduce by 51.1 kB

  • Original 554.6 kB
  • After minification 503.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. Whatrunswhere images are well optimized though.

JavaScript Optimization

-57%

Potential reduce by 189.6 kB

  • Original 332.8 kB
  • After minification 330.5 kB
  • After compression 143.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 189.6 kB or 57% of the original size.

CSS Optimization

-83%

Potential reduce by 238.3 kB

  • Original 287.8 kB
  • After minification 284.9 kB
  • After compression 49.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. Whatrunswhere.com needs all CSS files to be minified and compressed as it can save up to 238.3 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 34 (58%)

Requests Now

59

After Optimization

25

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

whatrunswhere.com

whatrunswhere.com

70 ms

www.whatrunswhere.com

www.whatrunswhere.com

67 ms

www.whatrunswhere.com

www.whatrunswhere.com

199 ms

css

css

64 ms

reset.min.css

reset.min.css

31 ms

tabs.min.css

tabs.min.css

62 ms

base.min.css

base.min.css

122 ms

skeleton.min.css

skeleton.min.css

93 ms

layout.css

layout.css

98 ms

jquery.fancybox-1.3.4.css

jquery.fancybox-1.3.4.css

97 ms

jquery.min.js

jquery.min.js

73 ms

validate.min.js

validate.min.js

138 ms

tabs.min.js

tabs.min.js

97 ms

jquery.fancybox-1.3.4.pack.js

jquery.fancybox-1.3.4.pack.js

136 ms

jquery.placeholder.js

jquery.placeholder.js

136 ms

conversion.js

conversion.js

46 ms

w.js

w.js

190 ms

v3d3IJdzbn4

v3d3IJdzbn4

114 ms

j.php

j.php

68 ms

ga.js

ga.js

123 ms

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

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

176 ms

50aa6fd9703a780002000152.js

50aa6fd9703a780002000152.js

172 ms

78 ms

bg.jpg

bg.jpg

94 ms

signIn.gif

signIn.gif

49 ms

WhatRunsWhere.jpg

WhatRunsWhere.jpg

94 ms

bg_dark.jpg

bg_dark.jpg

93 ms

app_1.jpg

app_1.jpg

131 ms

app_2.jpg

app_2.jpg

92 ms

app_3.jpg

app_3.jpg

169 ms

app_4.jpg

app_4.jpg

146 ms

mcsaatchi-t.jpg

mcsaatchi-t.jpg

146 ms

knowledgely-t.jpg

knowledgely-t.jpg

169 ms

stm-t.jpg

stm-t.jpg

146 ms

clients.jpg

clients.jpg

201 ms

bg_light.jpg

bg_light.jpg

239 ms

twitter.gif

twitter.gif

191 ms

facebook.gif

facebook.gif

191 ms

linkedin.gif

linkedin.gif

202 ms

google.gif

google.gif

202 ms

divider.jpg

divider.jpg

244 ms

WRW.jpg

WRW.jpg

245 ms

EFpQQyG9GqCrobXxL-KRMfEr6Hm6RMS0v1dtXsGir4g.ttf

EFpQQyG9GqCrobXxL-KRMfEr6Hm6RMS0v1dtXsGir4g.ttf

78 ms

s-BiyweUPV0v-yRb-cjciC3USBnSvpkopQaUR-2r7iU.ttf

s-BiyweUPV0v-yRb-cjciC3USBnSvpkopQaUR-2r7iU.ttf

121 ms

v.gif

v.gif

9 ms

www-embed-player-vflZsBgOl.css

www-embed-player-vflZsBgOl.css

115 ms

www-embed-player.js

www-embed-player.js

150 ms

83 ms

__utm.gif

__utm.gif

24 ms

225 ms

blank.gif

blank.gif

125 ms

tagjs

tagjs

42 ms

1eJU4PjErWSV5LNTKFXcze5UHikZLg3viIH581vcHWA.js

1eJU4PjErWSV5LNTKFXcze5UHikZLg3viIH581vcHWA.js

21 ms

ad_status.js

ad_status.js

90 ms

zN7GBFwfMP4uA6AR0HCoLQ.ttf

zN7GBFwfMP4uA6AR0HCoLQ.ttf

40 ms

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

70 ms

100 ms

adsct

adsct

144 ms

Pug

Pug

106 ms

pixel

pixel

85 ms

cb

cb

49 ms

cb

cb

17 ms

ncm

ncm

15 ms

sd

sd

26 ms

cb

cb

3 ms

help_left.png

help_left.png

32 ms

tap.php

tap.php

338 ms

nr-768.min.js

nr-768.min.js

96 ms

Accessibility Review

whatrunswhere.com accessibility score

64

Accessibility Issues

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

High

[aria-*] attributes do not match their roles

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

[aria-*] attributes do not have valid values

High

ARIA IDs are not unique

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

whatrunswhere.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

whatrunswhere.com SEO score

74

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

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 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 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

whatrunswhere.com

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