Tools & Wizards About Us
whoscored.info screenshot

Report Summary

  • 40

    Performance

    Renders faster than
    59% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

whoscored.info

Whoscored Football Livescore, Football Live Results Whoscored – Whoscored.info

Page Load Speed

4.7 sec in total

First Response

218 ms

Resources Loaded

2.3 sec

Page Rendered

2.2 sec

whoscored.info screenshot

About Website

Welcome to whoscored.info homepage info - get ready to check Whoscored best content right away, or after learning these important things about whoscored.info

Our experts at whoscored know which factors are going to play an important role in determining the outcome of a match. Singup now and start getting the winning tips from our processional tipsters.

Visit whoscored.info

Key Findings

We analyzed Whoscored.info page load time and found that the first response time was 218 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 70% of websites can load faster.

Performance Metrics

whoscored.info performance score

40

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.0 s

10/100

10%

LCP (Largest Contentful Paint)

Value8.6 s

1/100

25%

SI (Speed Index)

Value5.0 s

64/100

10%

TBT (Total Blocking Time)

Value570 ms

52/100

30%

CLS (Cumulative Layout Shift)

Value0.004

100/100

15%

TTI (Time to Interactive)

Value11.2 s

20/100

10%

Network Requests Diagram

whoscored.info

218 ms

www.whoscored.info

593 ms

bootstrap.css

27 ms

style.css

22 ms

jquery-2.1.3.min.js

309 ms

Our browser made a total of 50 requests to load all elements on the main page. We found that 92% of them (46 requests) were addressed to the original Whoscored.info, 4% (2 requests) were made to Googletagmanager.com and 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Whoscored.info.

Page Optimization Overview & Recommendations

Page size can be reduced by 479.1 kB (15%)

Content Size

3.3 MB

After Optimization

2.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Whoscored.info main page is 3.3 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. 65% of websites need less resources to load. Images take 2.6 MB which makes up the majority of the site volume.

HTML Optimization

-41%

Potential reduce by 235.9 kB

  • Original 577.8 kB
  • After minification 547.5 kB
  • After compression 341.9 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 235.9 kB or 41% of the original size.

Image Optimization

-9%

Potential reduce by 236.9 kB

  • Original 2.6 MB
  • After minification 2.3 MB

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. Whoscored images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 1.1 kB

  • Original 73.7 kB
  • After minification 73.7 kB
  • After compression 72.5 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. This website has mostly compressed JavaScripts.

CSS Optimization

-12%

Potential reduce by 5.1 kB

  • Original 44.5 kB
  • After minification 44.5 kB
  • After compression 39.4 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. Whoscored.info needs all CSS files to be minified and compressed as it can save up to 5.1 kB or 12% of the original size.

Requests Breakdown

Number of requests can be reduced by 13 (36%)

Requests Now

36

After Optimization

23

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

whoscored.info

whoscored.info

218 ms

www.whoscored.info

www.whoscored.info

593 ms

bootstrap.css

bootstrap.css

27 ms

style.css

style.css

22 ms

jquery-2.1.3.min.js

jquery-2.1.3.min.js

309 ms

font-awesome.min.css

font-awesome.min.css

13 ms

gtm.js

gtm.js

107 ms

logo.png

logo.png

33 ms

img-01.jpg

img-01.jpg

542 ms

dark-matter.png

dark-matter.png

195 ms

header-bg.jpg

header-bg.jpg

59 ms

roboto-regular-webfont.woff

roboto-regular-webfont.woff

280 ms

bootstrap.min.js

bootstrap.min.js

49 ms

owl.carousel.min.css

owl.carousel.min.css

49 ms

owl.theme.min.css

owl.theme.min.css

226 ms

owl.carousel.min.js

owl.carousel.min.js

51 ms

jquery.form.js

jquery.form.js

70 ms

mycustom.js

mycustom.js

83 ms

firebase.js

firebase.js

616 ms

notification.js

notification.js

84 ms

parnner.png

parnner.png

112 ms

Whoscored_Football_Livescore.jpg

Whoscored_Football_Livescore.jpg

143 ms

Football_Live_Results_Whoscored.jpg

Football_Live_Results_Whoscored.jpg

143 ms

ftr_img_1.png

ftr_img_1.png

162 ms

ftr_img_2.png

ftr_img_2.png

165 ms

ftr_img_3.png

ftr_img_3.png

176 ms

ftr_img_4.png

ftr_img_4.png

174 ms

ftr_img_5.png

ftr_img_5.png

190 ms

ftr_img_6.png

ftr_img_6.png

190 ms

ftr_img_7.png

ftr_img_7.png

380 ms

ftr_img_8.png

ftr_img_8.png

203 ms

nowscore.gif

nowscore.gif

213 ms

document-04-128.png

document-04-128.png

229 ms

mailIcon.png

mailIcon.png

421 ms

bebasneue-webfont.woff

bebasneue-webfont.woff

414 ms

glyphicons-halflings-regular.woff

glyphicons-halflings-regular.woff

514 ms

oswald-bold-webfont.woff

oswald-bold-webfont.woff

675 ms

mid_banner.jpg

mid_banner.jpg

1099 ms

subtle-dark-vertical.png

subtle-dark-vertical.png

585 ms

oswald-regular-webfont.woff

oswald-regular-webfont.woff

724 ms

analytics.js

analytics.js

31 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

775 ms

collect

collect

14 ms

js

js

104 ms

roboto-regular-webfont.ttf

roboto-regular-webfont.ttf

654 ms

bebasneue-webfont.ttf

bebasneue-webfont.ttf

551 ms

glyphicons-halflings-regular.ttf

glyphicons-halflings-regular.ttf

502 ms

oswald-bold-webfont.ttf

oswald-bold-webfont.ttf

437 ms

oswald-regular-webfont.ttf

oswald-regular-webfont.ttf

458 ms

fontawesome-webfont.ttf

fontawesome-webfont.ttf

529 ms

Accessibility Review

whoscored.info accessibility score

83

Accessibility Issues

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

whoscored.info best practices score

58

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Requests the notification permission on page load

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

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

whoscored.info SEO score

91

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

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Whoscored.info can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Whoscored.info 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

whoscored.info

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