Tools & Wizards About Us
scoreweek.com screenshot

Report Summary

  • 80

    Performance

    Renders faster than
    86% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 67% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

scoreweek.com

Page Load Speed

3 sec in total

First Response

581 ms

Resources Loaded

2.2 sec

Page Rendered

204 ms

scoreweek.com screenshot

About Website

Click here to check amazing Scoreweek content for Ireland. Otherwise, check out these important facts you probably never knew about scoreweek.com

SCOREWEEK is an online league information resource (results, fixtures & standings) for grassroots soccer around Ireland

Visit scoreweek.com

Key Findings

We analyzed Scoreweek.com page load time and found that the first response time was 581 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

scoreweek.com performance score

80

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

51/100

10%

LCP (Largest Contentful Paint)

Value3.7 s

58/100

25%

SI (Speed Index)

Value3.0 s

94/100

10%

TBT (Total Blocking Time)

Value180 ms

92/100

30%

CLS (Cumulative Layout Shift)

Value0.088

92/100

15%

TTI (Time to Interactive)

Value3.4 s

93/100

10%

Network Requests Diagram

scoreweek.com

581 ms

social_widget.css

144 ms

style.css

174 ms

reset.css

176 ms

slideshow.css

178 ms

Our browser made a total of 99 requests to load all elements on the main page. We found that 24% of them (24 requests) were addressed to the original Scoreweek.com, 8% (8 requests) were made to Apis.google.com and 7% (7 requests) were made to Googleads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (581 ms) belongs to the original domain Scoreweek.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 538.1 kB (63%)

Content Size

851.5 kB

After Optimization

313.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Scoreweek.com main page is 851.5 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. 70% of websites need less resources to load. Javascripts take 638.9 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 23.8 kB

  • Original 31.6 kB
  • After minification 29.1 kB
  • After compression 7.7 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.8 kB or 76% of the original size.

Image Optimization

-6%

Potential reduce by 9.2 kB

  • Original 159.0 kB
  • After minification 149.9 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. Scoreweek images are well optimized though.

JavaScript Optimization

-76%

Potential reduce by 487.9 kB

  • Original 638.9 kB
  • After minification 482.8 kB
  • After compression 151.0 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 487.9 kB or 76% of the original size.

CSS Optimization

-78%

Potential reduce by 17.1 kB

  • Original 22.0 kB
  • After minification 16.9 kB
  • After compression 4.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. Scoreweek.com needs all CSS files to be minified and compressed as it can save up to 17.1 kB or 78% of the original size.

Requests Breakdown

Number of requests can be reduced by 62 (66%)

Requests Now

94

After Optimization

32

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

scoreweek.com

scoreweek.com

581 ms

social_widget.css

social_widget.css

144 ms

style.css

style.css

174 ms

reset.css

reset.css

176 ms

slideshow.css

slideshow.css

178 ms

style.css

style.css

197 ms

Teknium

Teknium

176 ms

jquery-1.2.6.js

jquery-1.2.6.js

262 ms

jquery.cycle.js

jquery.cycle.js

267 ms

slideshow.js

slideshow.js

263 ms

jd.gallery.css

jd.gallery.css

262 ms

mootools.namespaced.js

mootools.namespaced.js

382 ms

jd.gallery.namespaced.js

jd.gallery.namespaced.js

289 ms

cookieconsent.latest.min.js

cookieconsent.latest.min.js

79 ms

show_ads.js

show_ads.js

5 ms

analytics.js

analytics.js

5 ms

195 ms

collect

collect

35 ms

background.png

background.png

175 ms

logo.png

logo.png

187 ms

mobile1.png

mobile1.png

185 ms

scoreweek_crest_left.png

scoreweek_crest_left.png

186 ms

ddsl_info_pane.jpg

ddsl_info_pane.jpg

183 ms

sdk.js

sdk.js

11 ms

plusone.js

plusone.js

175 ms

menuhover.gif

menuhover.gif

175 ms

header-bg.png

header-bg.png

263 ms

slider-bg.png

slider-bg.png

262 ms

ca-pub-3716901205824095.js

ca-pub-3716901205824095.js

161 ms

zrt_lookup.html

zrt_lookup.html

160 ms

show_ads_impl.js

show_ads_impl.js

63 ms

262 ms

xd_arbiter.php

xd_arbiter.php

141 ms

xd_arbiter.php

xd_arbiter.php

188 ms

ads

ads

319 ms

button.png

button.png

116 ms

footer-bg.png

footer-bg.png

117 ms

osd.js

osd.js

63 ms

ads

ads

270 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

64 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

65 ms

fastbutton

fastbutton

129 ms

ads

ads

238 ms

postmessageRelay

postmessageRelay

53 ms

like.php

like.php

93 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

23 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

22 ms

pJeswbKZO4XwVR0035gpgvesZW2xOQ-xsNqO47m55DA.ttf

pJeswbKZO4XwVR0035gpgvesZW2xOQ-xsNqO47m55DA.ttf

42 ms

3193398744-postmessagerelay.js

3193398744-postmessagerelay.js

27 ms

rpc:shindig_random.js

rpc:shindig_random.js

32 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

15 ms

TY3MhkXpWJ-.js

TY3MhkXpWJ-.js

65 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

59 ms

129 ms

adj

adj

140 ms

beacon

beacon

125 ms

128 ms

adj

adj

133 ms

beacon

beacon

124 ms

img;p=11022203319335;idfa=;idfa_lat=;aaid=;aaid_lat=;cache=2140382759

img;p=11022203319335;idfa=;idfa_lat=;aaid=;aaid_lat=;cache=2140382759

148 ms

2251740349518870668

2251740349518870668

77 ms

abg.js

abg.js

79 ms

m_js_controller.js

m_js_controller.js

90 ms

googlelogo_color_112x36dp.png

googlelogo_color_112x36dp.png

73 ms

s

s

27 ms

x_button_blue2.png

x_button_blue2.png

31 ms

15 ms

0

0

153 ms

surly.js

surly.js

125 ms

28 ms

click%253Fd%253DAPEucNWP30jFe1gctAhdQQaZEkcCEq6AiXNNJM9mifoAVoDdlTDr54XgAr628Hem1zZ_bKJFgXuTlEz6cHiScAVAl45Grl4Jgg%2526r1%253D;ord=1458466803;dc_lat=;dc_rdid=;tag_for_child_directed_treatment=

click%253Fd%253DAPEucNWP30jFe1gctAhdQQaZEkcCEq6AiXNNJM9mifoAVoDdlTDr54XgAr628Hem1zZ_bKJFgXuTlEz6cHiScAVAl45Grl4Jgg%2526r1%253D;ord=1458466803;dc_lat=;dc_rdid=;tag_for_child_directed_treatment=

343 ms

verify_selector.js

verify_selector.js

339 ms

blank.gif

blank.gif

341 ms

click%253Fd%253DAPEucNWButu2f4r3FvkSgukJaMvEN4AV0pBnhsjXDwtllXw7hRLOAvkX4eTBIfBJMPQb46MgQ8zCVVNxQyTqDXd_38mxI5cs9Q%2526r1%253D;ord=1458466803;dc_lat=;dc_rdid=;tag_for_child_directed_treatment=

click%253Fd%253DAPEucNWButu2f4r3FvkSgukJaMvEN4AV0pBnhsjXDwtllXw7hRLOAvkX4eTBIfBJMPQb46MgQ8zCVVNxQyTqDXd_38mxI5cs9Q%2526r1%253D;ord=1458466803;dc_lat=;dc_rdid=;tag_for_child_directed_treatment=

329 ms

verify_selector.js

verify_selector.js

377 ms

blank.gif

blank.gif

318 ms

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

50 ms

ba.html

ba.html

24 ms

pixel

pixel

53 ms

pixel

pixel

53 ms

4.gif

4.gif

50 ms

lidar.js

lidar.js

23 ms

sbhK2lTE.js

sbhK2lTE.js

22 ms

4311.js

4311.js

34 ms

cTrvNaRi.html

cTrvNaRi.html

20 ms

verifyr.js

verifyr.js

88 ms

dt

dt

136 ms

dt

dt

113 ms

verifyr.js

verifyr.js

62 ms

skeleton.gif

skeleton.gif

94 ms

skeleton.gif

skeleton.gif

92 ms

beacon.js

beacon.js

60 ms

0

0

40 ms

sd

sd

6 ms

dtc

dtc

21 ms

dtc

dtc

19 ms

box_19_top-right.png

box_19_top-right.png

23 ms

ci.png

ci.png

16 ms

ui

ui

38 ms

Accessibility Review

scoreweek.com accessibility score

87

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.

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

Document doesn't have a <title> element

Best Practices

scoreweek.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

scoreweek.com SEO score

75

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

Document doesn't have a <title> element

Crawling and Indexing

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

Impact

Issue

High

Page is blocked from indexing

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

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Scoreweek.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Scoreweek.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

scoreweek.com

Open Graph data is detected on the main page of Scoreweek. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: