livescores.com

livescores.com is SSL secured

Free website and domain report on livescores.com

Last Updated: 24th February, 2024
Overview

Snoop Summary for livescores.com

This is a free and comprehensive report about livescores.com. Our records indicate that livescores.com is owned/operated by Livescore Limited. Livescores.com is expected to earn an estimated $1,284 USD per day from advertising revenue. The sale of livescores.com would possibly be worth $936,991 USD. This figure is based on the daily revenue potential of the website over a 24 month period. Livescores.com receives an estimated 204,550 unique visitors every day - an insane amount of traffic! This report was last updated 24th February, 2024.

About livescores.com

Site Preview: livescores.com livescores.com
Title: Soccer Live Scores | Latest Results & Fixtures
Description: Soccer LiveScore - the 1st live score service on the Internet, powered by LiveScore.com, no.1 ranked Soccer website. Over 1000 live soccer games weekly, from every corner of the World.
Keywords and Tags: gambling related, livescore, livescore com, livescore football, livescore powered, livescore today, livescores com, popular, sports, www livescore com, www livescores com
Related Terms: best defenders in soccer, fox soccer channel, manager online soccer, online soccer manager best team, osm soccer, play soccer manager online, smart soccer ball, soccer logo, soccer physics, soccer wallpaper
Fav Icon:
Age: Over 25 years old
Domain Created: 4th November, 1998
Domain Updated: 30th October, 2023
Domain Expires: 3rd November, 2024
Review

Snoop Score

4/5 (Excellent!)

Valuation

$936,991 USD
Note: All valuation figures are estimates.

Popularity

Very High
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 8,491
Alexa Reach:
SEMrush Rank (US): 143,009
SEMrush Authority Score: 53
Moz Domain Authority: 0
Moz Page Authority: 0

Organic vs Paid (Google Ads)

Organic Paid
Keywords: 14,357 0
Traffic: 11,438 0
Cost: $8,888 USD $0 USD
Traffic

Visitors

Daily Visitors: 204,550
Monthly Visitors: 6,225,858
Yearly Visitors: 74,660,750
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $1,284 USD
Monthly Revenue: $39,067 USD
Yearly Revenue: $468,491 USD
Note: All revenue figures are estimates.

Revenue By Country

SEO

Backlinks Analysis (SEMrush)

Backlinks: 327,482
Referring Domains: 1,495
Referring IPs: 968
Livescores.com has 327,482 backlinks according to SEMrush. 99% of these backlinks are "dofollow" (follow) links which allow the flow of link equity to pass through, which may improve livescores.com's search engine rankings. Other links are treated as 'hints' by search engines and may also pass link equity, depending on what search engines decide in each case.
100% of livescores.com's backlinks are text and image links, which are ideal for SEO. Other backlink types may be unrecognized or ignored by search engines.

Top New Follow Links

1
Source: http://www.showyoursearch.com/ke/q/3671276/Neroca-FC
Target: http://www.livescores.com/

2
Source: http://crazzymindz.blogspot.com/2008/03/
Target: http://livescores.com/

3
Source: http://web-search.marketing/the_worlds_most_visited_web_pages_33/
Target: http://www.livescores.com/

4
Source: https://markosweb.com/www/livescores.com/
Target: https://livescores.com/

5
Source: http://livescore.com.tr/euro/team-finland/
Target: http://www.livescores.com/

Top Ranking Keywords (US)

1
Keyword: livescore
Ranked Page: http://www.livescores.com/

2
Keyword: livescores com
Ranked Page: http://www.livescores.com/

3
Keyword: www livescores com
Ranked Page: http://www.livescores.com/

4
Keyword: livescore com
Ranked Page: http://www.livescores.com/

5
Keyword: www livescores com
Ranked Page: http://www.livescores.com/soccer/live/

Domain Analysis

Value Length
Domain: livescores.com 14
Domain Name: livescores 10
Extension (TLD): com 3
Expiry Check:

Page Speed Analysis

Average Load Time: 0.89 seconds
Load Time Comparison: Faster than 77% of sites

PageSpeed Insights

Avg. (All Categories) 84
Performance 93
Accessibility 90
Best Practices 83
SEO 100
PWA 56
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://www.livescores.com/
Updated: 17th November, 2022

0.91 seconds
First Contentful Paint (FCP)
90%
5%
5%

0.01 seconds
First Input Delay (FID)
94%
4%
2%

Simulate loading on desktop
93

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for livescores.com. This includes details about optimizing page load times which can result in a better user experience.

Metrics

First Contentful Paint — 0.7 s
The time taken for the first image or text on the page to be rendered.
Time to Interactive — 2.2 s
The time taken for the page to become fully interactive.
Speed Index — 1.0 s
The time taken for the page contents to be visibly populated.
Total Blocking Time — 130 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).
Cumulative Layout Shift — 0.01
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Audits

Max Potential First Input Delay — 130 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 0.9 s
The time taken for the primary content of the page to be rendered.
Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://livescores.com/
http/1.1
0
30.343999853358
398
0
301
text/html
https://www.livescores.com/
h2
30.649999855086
227.99000004306
22604
206509
200
text/html
Document
https://fonts.googleapis.com/css2?family=Roboto:wght@400;700&display=swap
h2
236.71899992041
255.40699996054
1421
4396
200
text/css
Stylesheet
https://www.livescores.com/ls-web-assets/js/ls.bundle-919a6747d6dd94b8fba76ed660fb3b12.js
h2
236.96499993093
276.26099996269
10036
27624
200
application/javascript
Script
https://www.livescores.com/_next/static/css/1184e4c1cc17d22bf0e7.css
h2
237.38299985416
349.19199999422
1290
2266
200
text/css
Stylesheet
https://www.livescores.com/_next/static/css/69d813229c3e3dc60fe0.css
h2
237.72199987434
247.52199999057
4820
14799
200
text/css
Stylesheet
https://www.livescores.com/_next/static/css/00bbbe9968a2b5ba69a3.css
h2
237.86700004712
247.10000003688
5285
20327
200
text/css
Stylesheet
https://cdn3.livescore.com/web2/img/fb_like_disabled.png
h2
262.90600001812
429.12200000137
2235
1447
200
image/png
Image
https://www.googletagmanager.com/gtm.js?id=GTM-MGW6C35
h2
263.06200004183
278.02699990571
61122
172664
200
application/javascript
Script
https://www.googletagservices.com/tag/js/gpt.js
h2
263.23299994692
270.17299993895
28175
80579
200
text/javascript
Script
https://securepubads.g.doubleclick.net/gpt/pubads_impl_2022111001.js?cb=31070943
h2
295.34399998374
309.36499987729
133317
391651
200
text/javascript
Script
https://securepubads.g.doubleclick.net/pagead/ppub_config?ippd=www.livescores.com
h2
302.1759998519
315.0809998624
1052
194
200
application/json
XHR
https://www.google-analytics.com/analytics.js
h2
339.82799993828
345.61199997552
20663
50230
200
text/javascript
Script
https://www.google-analytics.com/plugins/ua/linkid.js
h2
402.19299984165
409.82399997301
1680
1569
200
text/javascript
Script
https://geo.livescore.com/me/
h2
418.89499989338
528.8129998371
291
19
200
application/javascript
Script
https://www.livescores.com/ls-web-assets/images/ls_header@2x-306292c9dad310aba03909053040d5c6.jpg
h2
431.05500005186
663.69799990207
44809
44029
200
image/jpeg
Image
https://www.google-analytics.com/j/collect?v=1&_v=j98&a=988588273&t=pageview&_s=1&dl=https%3A%2F%2Fwww.livescores.com%2F&ul=en-us&de=UTF-8&dt=Soccer%20Live%20Scores%20-%20powered%20by%20LiveScore.com&sd=24-bit&sr=800x600&vp=1350x940&je=0&_u=aGBACEAjBAAAACAEK~&jid=1825669020&gjid=806890444&cid=1417362321.1668668260&tid=UA-121657370-1&_gid=370538675.1668668260&_r=1&gtm=2wgb90MGW6C35&cd2=2022-11-16T22%3A57%3A39.905-08%3A00&cd3=1668668259905.e6ntqvta&cd5=GTM-MGW6C35&cd6=&cd7=TYPE_NAVIGATE&cd8=0&cd13=Mozilla%2F5.0%20(Macintosh%3B%20Intel%20Mac%20OS%20X%2010_15_7)%20AppleWebKit%2F537.36%20(KHTML%2C%20like%20Gecko)%20Chrome%2F98.0.4695.0%20Safari%2F537.36%20Chrome-Lighthouse&cd15=https%3A%2F%2Fwww.livescores.com%2F&cd17=GTM-MGW6C35_68&cd1=1417362321.1668668260&cd4=pageview&z=454474072
h2
440.22500002757
444.27099986933
617
2
200
text/plain
XHR
https://stats.g.doubleclick.net/j/collect?t=dc&aip=1&_r=3&v=1&_v=j98&tid=UA-121657370-1&cid=1417362321.1668668260&jid=1825669020&gjid=806890444&_gid=370538675.1668668260&_u=aGBACEAiBAAAACAEK~&z=1939000926
h2
472.75099996477
479.09799986519
690
2
200
text/plain
XHR
data
476.84799996205
477.0370000042
0
468
200
image/svg+xml
Image
https://www.livescores.com/ls-web-assets/svgs/common/warning-859eac02650c539cd8dd5acbd39ceaef.svg
h2
577.48199999332
815.56500005536
1227
696
200
image/svg+xml
Image
https://www.livescores.com/ls-web-assets/svgs/common/toggle-50e0f9b80491c1e5135b9836442c308b.svg
h2
577.73699983954
591.01299988106
1098
424
200
image/svg+xml
Image
https://www.livescores.com/ls-web-assets/svgs/common/cristianoRonaldo-b52670bcc6431c5e45c4ce4c5c4befb4.svg
h2
577.8299998492
617.51899984665
4846
11004
200
image/svg+xml
Image
https://www.google.com/ads/ga-audiences?t=sr&aip=1&_r=4&slf_rd=1&v=1&_v=j98&tid=UA-121657370-1&cid=1417362321.1668668260&jid=1825669020&_u=aGBACEAiBAAAACAEK~&z=234351773
h2
590.92399990186
601.47899994627
673
42
200
image/gif
Image
https://www.livescores.com/
h2
1086.0019999091
1192.347999895
435
0
200
text/html
XHR
https://www.livescores.com/?tz=-8
h2
1195.8409999497
1388.2939999457
23512
188569
200
text/html
Document
https://fonts.googleapis.com/css2?family=Roboto:wght@400;700&display=swap
h2
1404.1599999182
1404.3240000028
1421
4396
200
text/css
Stylesheet
https://www.livescores.com/ls-web-assets/js/ls.bundle-919a6747d6dd94b8fba76ed660fb3b12.js
h2
1404.4139999896
1404.5259999111
10036
27624
200
application/javascript
Script
https://www.livescores.com/_next/static/css/1184e4c1cc17d22bf0e7.css
h2
1404.6109998599
1404.7119999304
1290
2266
200
text/css
Stylesheet
https://www.livescores.com/_next/static/css/69d813229c3e3dc60fe0.css
h2
1404.8170000315
1404.9100000411
4820
14799
200
text/css
Stylesheet
https://www.livescores.com/_next/static/css/00bbbe9968a2b5ba69a3.css
h2
1405.2629999351
1405.4300000425
5285
20327
200
text/css
Stylesheet
https://cdn3.livescore.com/web2/img/fb_like_disabled.png
h2
1405.5459999945
1405.7699998375
2235
1447
200
image/png
Image
https://www.googletagmanager.com/gtm.js?id=GTM-MGW6C35
h2
1413.1199999247
1413.2840000093
61122
172664
200
application/javascript
Script
https://www.googletagservices.com/tag/js/gpt.js
h2
1413.5729998816
1413.705999963
28175
80579
200
text/javascript
Script
https://geo.livescore.com/me/
h2
1418.6469998676
1523.9629999269
291
19
200
application/javascript
Script
https://www.livescores.com/ls-web-assets/images/ls_header@2x-306292c9dad310aba03909053040d5c6.jpg
h2
1418.7379998621
1418.8759999815
44809
44029
200
image/jpeg
Image
https://securepubads.g.doubleclick.net/gpt/pubads_impl_2022111001.js?cb=31070943
h2
1467.9809999652
1468.215999892
133317
391651
200
text/javascript
Script
https://securepubads.g.doubleclick.net/pagead/ppub_config?ippd=www.livescores.com
h2
1471.2539999746
1477.1259999834
1052
194
200
application/json
XHR
https://www.google-analytics.com/analytics.js
h2
1502.739999909
1503.0030000489
20663
50230
200
text/javascript
Script
https://www.google-analytics.com/plugins/ua/linkid.js
h2
1602.2220000159
1602.4519999046
1680
1569
200
text/javascript
Script
https://www.livescores.com/ls-web-assets/svgs/common/warning-859eac02650c539cd8dd5acbd39ceaef.svg
h2
1626.4400000218
1626.6260000411
1227
696
200
image/svg+xml
Image
https://www.livescores.com/ls-web-assets/svgs/common/toggle-50e0f9b80491c1e5135b9836442c308b.svg
h2
1631.34299987
1631.4870000351
1098
424
200
image/svg+xml
Image
https://www.livescores.com/ls-web-assets/svgs/common/cristianoRonaldo-b52670bcc6431c5e45c4ce4c5c4befb4.svg
h2
1631.8049998954
1631.9209998474
4846
11004
200
image/svg+xml
Image
data
1642.1999998856
1642.2929998953
0
468
200
image/svg+xml
Image
https://www.google-analytics.com/collect?v=1&_v=j98&a=1580689347&t=pageview&_s=1&dl=https%3A%2F%2Fwww.livescores.com%2F%3Ftz%3D-8&ul=en-us&de=UTF-8&dt=Soccer%20Live%20Scores%20-%20powered%20by%20LiveScore.com&sd=24-bit&sr=800x600&vp=1350x940&je=0&_u=SCCACEAjBAAAAAAEK~&jid=&gjid=&cid=1417362321.1668668260&tid=UA-121657370-1&_gid=370538675.1668668260&gtm=2wgb90MGW6C35&cd2=2022-11-16T22%3A57%3A41.68-08%3A00&cd3=1668668261068.ol2eqm28&cd5=GTM-MGW6C35&cd6=https%3A%2F%2Fwww.livescores.com%2F&cd7=TYPE_NAVIGATE&cd8=0&cd13=Mozilla%2F5.0%20(Macintosh%3B%20Intel%20Mac%20OS%20X%2010_15_7)%20AppleWebKit%2F537.36%20(KHTML%2C%20like%20Gecko)%20Chrome%2F98.0.4695.0%20Safari%2F537.36%20Chrome-Lighthouse&cd15=https%3A%2F%2Fwww.livescores.com%2F%3Ftz%3D-8&cd17=GTM-MGW6C35_68&cd1=1417362321.1668668260&cd4=pageview&z=538424232
h2
1667.6519999746
1671.4689999353
597
35
200
image/gif
Image
https://www.livescores.com/ls-web-assets/svgs/common/pen-c123be2d2cddf58c8a19666c56baa302.svg
h2
1730.3509998601
1936.1119999085
1335
849
200
image/svg+xml
Image
https://www.livescores.com/?tz=-8
h2
2142.7609999664
2236.6720000282
433
0
200
text/html
XHR
https://cdn-ukwest.onetrust.com/scripttemplates/otSDKStub.js
h2
2238.2429998834
2306.3429999165
8044
21748
200
application/javascript
Script
https://js-sec.indexww.com/ht/p/188832-82910719724410.js
h2
2238.4659999516
2272.6960000582
42634
146502
200
text/javascript
Script
https://api.rlcdn.com/api/identity?pid=2&rt=envelope
h2
2297.7390000597
2333.2080000546
426
0
204
text/plain
XHR
https://match.adsrvr.org/track/rid?ttd_pid=casale&fmt=json&p=188832&gdpr=1
h2
2299.2179999128
2318.6989999376
518
63
200
application/json
XHR
https://cdn-ukwest.onetrust.com/consent/55d519ea-ef26-44f4-843d-07646ab5eb8d/55d519ea-ef26-44f4-843d-07646ab5eb8d.json
h2
2313.5889999103
2350.3359998576
2230
3130
200
application/x-javascript
XHR
https://geolocation.onetrust.com/cookieconsentpub/v1/geo/location
h2
2353.5970000084
2380.5789998733
465
75
200
application/json
XHR
https://cdn-ukwest.onetrust.com/scripttemplates/6.31.0/otBannerSdk.js
h2
2394.9219998904
2442.9209998343
81849
342379
200
application/javascript
Script
https://cdn-ukwest.onetrust.com/consent/55d519ea-ef26-44f4-843d-07646ab5eb8d/16aaaff8-4c8c-4fe9-a68a-1bf23e7e7e8f/en.json
h2
2471.4989999775
2520.6819998566
30593
175232
200
application/x-javascript
Fetch
https://cdn-ukwest.onetrust.com/vendorlist/iab2Data.json
h2
2471.8379999977
2534.6279998776
53664
369825
200
application/x-javascript
Fetch
https://cdn-ukwest.onetrust.com/scripttemplates/6.31.0/otTCF.js
h2
2473.3080000151
2512.037999928
15846
69319
200
application/javascript
Script
https://cdn-ukwest.onetrust.com/scripttemplates/6.31.0/assets/otFlat.json
h2
2669.3159998395
2711.7939998861
3847
12867
200
application/json
Fetch
https://cdn-ukwest.onetrust.com/scripttemplates/6.31.0/assets/v2/otPcCenter.json
h2
2669.7939999867
2742.6050000358
12446
48587
200
application/json
Fetch
https://cdn-ukwest.onetrust.com/scripttemplates/6.31.0/assets/otCookieSettingsButton.json
h2
2670.4839998856
2719.6899999399
2666
4753
200
application/json
Fetch
https://cdn-ukwest.onetrust.com/scripttemplates/6.31.0/assets/otCommonStyles.css
h2
2671.0240000393
2712.8649998922
5022
21289
200
text/css
Fetch
https://fonts.gstatic.com/s/roboto/v30/KFOlCnqEu92Fr1MmWUlfBBc4AMP6lQ.woff2
h2
2773.3960000332
2777.5159999728
11968
11040
200
font/woff2
Font
https://fonts.gstatic.com/s/roboto/v30/KFOmCnqEu92Fr1Mu4mxKKTU1Kg.woff2
h2
2773.5460000113
2777.1149999462
11954
11028
200
font/woff2
Font
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
-962.909
11.918
-936.261
5.603
-914.713
21.479
-876.434
10.296
-866.112
14.162
-845.564
45.334
-796.157
19.561
-771.99
8.932
-760.225
6.716
-753.494
6.543
-746.917
23.541
-721.208
100.178
-620.948
10.863
-608.28
7.759
-581.508
6.702
-565.756
5.406
-528.371
7.171
-375.438
7.394
-110.836
111.009
197.329
20.024
217.625
8.052
231.014
24.758
255.794
24.997
281.786
13.707
295.528
15.695
311.807
77.793
395.526
5.773
401.377
18.696
423.568
43.796
467.607
6.187
474.203
61.681
745.504
5.729
946.71
99.486
1085.914
18.921
1187.257
12.85
1201.66
14.924
1265.763
13.793
1323.982
7.4
1342.694
7.768
1350.492
126.905
1550.813
112.875
1670.045
8.548
1695.016
11.763
2061.19
5.35
2095.345
5.922
2159.509
5.262
2239.654
5.539
2270.489
5.658
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Other

Eliminate render-blocking resources
Resources, such as JavaScript and style sheets, can block the first paint of the page. Livescores.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
Properly size images — Potential savings of 32 KiB
Images can slow down the page's load time. Livescores.com should consider serving more appropriate-sized images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.livescores.com/ls-web-assets/images/ls_header@2x-306292c9dad310aba03909053040d5c6.jpg
44029
32899
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Livescores.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Livescores.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Livescores.com should consider minifying JS files.
Reduce unused CSS — Potential savings of 15 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Livescores.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Transfer Size (Bytes) Potential Savings (Bytes)
#onetrust-banner-sdk{-ms-text-size-adjust:100%;-webkit-text-size-adjust:100%} ...
18231
14980
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 190 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
https://www.livescores.com/?tz=-8
193.448
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Livescores.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers — Potential savings of 6 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
URL Potential Savings (Bytes)
https://cdn-ukwest.onetrust.com/scripttemplates/6.31.0/otBannerSdk.js
6537
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
URL Potential Savings (Ms)
https://www.livescores.com/ls-web-assets/images/ls_header@2x-306292c9dad310aba03909053040d5c6.jpg
0
Avoids enormous network payloads — Total size was 959 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://securepubads.g.doubleclick.net/gpt/pubads_impl_2022111001.js?cb=31070943
133317
https://securepubads.g.doubleclick.net/gpt/pubads_impl_2022111001.js?cb=31070943
133317
https://cdn-ukwest.onetrust.com/scripttemplates/6.31.0/otBannerSdk.js
81849
https://www.googletagmanager.com/gtm.js?id=GTM-MGW6C35
61122
https://www.googletagmanager.com/gtm.js?id=GTM-MGW6C35
61122
https://cdn-ukwest.onetrust.com/vendorlist/iab2Data.json
53664
https://www.livescores.com/ls-web-assets/images/ls_header@2x-306292c9dad310aba03909053040d5c6.jpg
44809
https://www.livescores.com/ls-web-assets/images/ls_header@2x-306292c9dad310aba03909053040d5c6.jpg
44809
https://js-sec.indexww.com/ht/p/188832-82910719724410.js
42634
https://cdn-ukwest.onetrust.com/consent/55d519ea-ef26-44f4-843d-07646ab5eb8d/16aaaff8-4c8c-4fe9-a68a-1bf23e7e7e8f/en.json
30593
Avoid chaining critical requests — 1 chain found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Livescores.com should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 0.7 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://www.livescores.com/?tz=-8
484.366
6.328
3.241
Unattributable
229.752
102.144
0
https://www.livescores.com/ls-web-assets/js/ls.bundle-919a6747d6dd94b8fba76ed660fb3b12.js
225.242
222.59
2.392
https://cdn-ukwest.onetrust.com/scripttemplates/6.31.0/otBannerSdk.js
127.547
68.29
8.035
https://securepubads.g.doubleclick.net/gpt/pubads_impl_2022111001.js?cb=31070943
123.687
85.127
38.27
https://www.googletagmanager.com/gtm.js?id=GTM-MGW6C35
82.424
61.836
17.254
https://www.googletagservices.com/tag/js/gpt.js
53.28
42.659
8.63
Minimizes main-thread work — 1.5 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Script Evaluation
678.423
Style & Layout
234.22
Other
198.86
Rendering
151.347
Script Parsing & Compilation
90.807
Parse HTML & CSS
59.287
Garbage Collection
55.952
All text remains visible during webfont loads
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
Keep request counts low and transfer sizes small — 60 requests • 959 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
60
982200
Script
18
658941
Other
17
116554
Image
13
111035
Document
2
46116
Stylesheet
8
25632
Font
2
23922
Media
0
0
Third-party
38
786661
Minimize third-party usage — Third-party code blocked the main thread for 0 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Transfer Size (Bytes) Main-Thread Blocking Time (Ms)
325778
0
216672
0
122244
0
45900
0
42634
0
26764
0
673
0
518
0
426
0
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Avoid large layout shifts — 1 element found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.0098234830575256
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks — 6 long tasks found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
Unattributable
2098
127
https://www.livescores.com/ls-web-assets/js/ls.bundle-919a6747d6dd94b8fba76ed660fb3b12.js
399
111
https://www.livescores.com/ls-web-assets/js/ls.bundle-919a6747d6dd94b8fba76ed660fb3b12.js
1305
99
https://securepubads.g.doubleclick.net/gpt/pubads_impl_2022111001.js?cb=31070943
1840
78
https://cdn-ukwest.onetrust.com/scripttemplates/6.31.0/otBannerSdk.js
2225
56
https://www.livescores.com/?tz=-8
338
50
Avoid non-composited animations — 1 animated element found
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Element Name
Image elements have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of livescores.com on mobile screens.
Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.

Budgets

Performance budget
It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.
Timing budget
It is advised to set a timing budget to monitor the performance of your site.

Metrics

Largest Contentful Paint — 1.4 s
The timing of the largest text or image that is painted.

Other

Reduce unused JavaScript — Potential savings of 179 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://securepubads.g.doubleclick.net/gpt/pubads_impl_2022111001.js?cb=31070943
133317
97820
https://cdn-ukwest.onetrust.com/scripttemplates/6.31.0/otBannerSdk.js
81849
36894
https://www.googletagmanager.com/gtm.js?id=GTM-MGW6C35
61122
25857
https://js-sec.indexww.com/ht/p/188832-82910719724410.js
42634
22641
Serve static assets with an efficient cache policy — 10 resources found
Livescores.com can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
https://geo.livescore.com/me/
0
291
https://geo.livescore.com/me/
0
291
https://www.google-analytics.com/plugins/ua/linkid.js
3600000
1680
https://www.google-analytics.com/plugins/ua/linkid.js
3600000
1680
https://www.google-analytics.com/analytics.js
7200000
20663
https://www.google-analytics.com/analytics.js
7200000
20663
https://js-sec.indexww.com/ht/p/188832-82910719724410.js
14400000
42634
https://cdn-ukwest.onetrust.com/scripttemplates/6.31.0/otBannerSdk.js
86400000
81849
https://cdn-ukwest.onetrust.com/scripttemplates/6.31.0/otTCF.js
86400000
15846
https://cdn-ukwest.onetrust.com/scripttemplates/otSDKStub.js
86400000
8044

Other

Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
Avoid multiple page redirects — Potential savings of 1,400 ms
Redirects can cause additional delays before the page can begin loading. Livescores.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://livescores.com/
860
https://www.livescores.com/
544
https://www.livescores.com/?tz=-8
0
Avoid an excessive DOM size — 3,404 elements
A large DOM (Document Object Model) will increase memory usage, cause longer system calculations as well as costly layout reflows.
Statistic Element Value
Total DOM Elements
3404
Maximum DOM Depth
15
Maximum Child Elements
179
Largest Contentful Paint image was lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Element
90

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of livescores.com. This includes details about various page attributes that can be optimized.

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
Heading elements appear in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`button`, `link`, and `menuitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
ARIA `meter` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `progressbar` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
ARIA `tooltip` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `treeitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.
Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Names and labels

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Links have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.
`<object>` elements have alternate text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Internationalization and localization

`<html>` element has a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Livescores.com may provide assistance to deaf or hearing-impaired users with captions on videos.

Names and labels

Buttons do not have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Failing Elements

Contrast

Background and foreground colors do not have a sufficient contrast ratio.
Many (if not most) users find low-contrast text difficult or impossible to read.
Failing Elements

Manual Checks

The page has a logical tab order
The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.
Interactive controls are keyboard focusable
Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.
Interactive elements indicate their purpose and state
Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.
The user's focus is directed to new content added to the page
When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.
User focus is not accidentally trapped in a region
Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.
Custom controls have associated labels
Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.
Custom controls have ARIA roles
Ensure that all custom interactive controls have appropriate ARIA roles.
Visual order on the page follows DOM order
Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.
Offscreen content is hidden from assistive technology
Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.
HTML5 landmark elements are used to improve navigation
Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.
83

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that livescores.com should incorporate. This includes practices such as protecting pages with HTTPS.

Audits

Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids front-end JavaScript libraries with known security vulnerabilities
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).
Description Directive Severity
No CSP found in enforcement mode
High

Audits

Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.
Serves images with appropriate resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

Audits

Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Properly defines charset
It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL Request Resolution
http://livescores.com/
Allowed

Audits

Uses deprecated APIs — 2 warnings found
Avoid deprecated APIs which will eventually be removed the browser.
Deprecation / Warning Source
Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to the end user’s experience. For more help, check https://xhr.spec.whatwg.org/.
Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to the end user’s experience. For more help, check https://xhr.spec.whatwg.org/.
100

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for livescores.com. This includes optimizations such as providing meta data.

Mobile Friendly

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of livescores.com on mobile screens.
Document uses legible font sizes
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Tap targets are sized appropriately
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Document has a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the content.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Links are crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Manual Checks

Structured data is valid
Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
56

PWA

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of livescores.com. This includes details about web app manifests.

Installable

Web app manifest and service worker meet the installability requirements
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.

PWA Optimized

Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of livescores.com on mobile screens.
Provides a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.

PWA Optimized

Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.
Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.
Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.
Avg. (All Categories) 71
Performance 42
Accessibility 90
Best Practices 75
SEO 96
PWA 50
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://www.livescores.com/
Updated: 17th November, 2022

2.29 seconds
First Contentful Paint (FCP)
68%
14%
18%

0.31 seconds
First Input Delay (FID)
25%
49%
26%

Simulate loading on mobile
42

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for livescores.com. This includes details about optimizing page load times which can result in a better user experience.

Metrics

Cumulative Layout Shift — 0.002
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

Properly size images
Images can slow down the page's load time. Livescores.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Livescores.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Livescores.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Livescores.com should consider minifying JS files.
Reduce unused CSS — Potential savings of 15 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Livescores.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Transfer Size (Bytes) Potential Savings (Bytes)
#onetrust-banner-sdk{-ms-text-size-adjust:100%;-webkit-text-size-adjust:100%} ...
18232
15191
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 20 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
https://www.livescores.com/?tz=-8
23.186
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Livescores.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers — Potential savings of 6 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
URL Potential Savings (Bytes)
https://cdn-ukwest.onetrust.com/scripttemplates/6.31.0/otBannerSdk.js
6537
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
URL Potential Savings (Ms)
https://www.livescores.com/ls-web-assets/images/ls_header@2x-306292c9dad310aba03909053040d5c6.jpg
0
Avoids enormous network payloads — Total size was 959 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://securepubads.g.doubleclick.net/gpt/pubads_impl_2022111001.js
133318
https://securepubads.g.doubleclick.net/gpt/pubads_impl_2022111001.js
133318
https://cdn-ukwest.onetrust.com/scripttemplates/6.31.0/otBannerSdk.js
81849
https://www.googletagmanager.com/gtm.js?id=GTM-MGW6C35
61122
https://www.googletagmanager.com/gtm.js?id=GTM-MGW6C35
61122
https://cdn-ukwest.onetrust.com/vendorlist/iab2Data.json
53664
https://www.livescores.com/ls-web-assets/images/ls_header@2x-306292c9dad310aba03909053040d5c6.jpg
44819
https://www.livescores.com/ls-web-assets/images/ls_header@2x-306292c9dad310aba03909053040d5c6.jpg
44819
https://js-sec.indexww.com/ht/p/188832-82910719724410.js
42559
https://cdn-ukwest.onetrust.com/consent/55d519ea-ef26-44f4-843d-07646ab5eb8d/16aaaff8-4c8c-4fe9-a68a-1bf23e7e7e8f/en.json
30593
Avoid chaining critical requests — 1 chain found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Livescores.com should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
All text remains visible during webfont loads
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
Keep request counts low and transfer sizes small — 60 requests • 959 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
60
982341
Script
18
658862
Other
17
116593
Image
13
111100
Document
2
46149
Stylesheet
8
25714
Font
2
23923
Media
0
0
Third-party
38
786692
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Avoid large layout shifts — 2 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.0022199746079283
3.1333957506744E-6
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks — 20 long tasks found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
https://js-sec.indexww.com/ht/p/188832-82910719724410.js
8997
645
https://securepubads.g.doubleclick.net/gpt/pubads_impl_2022111001.js
8520
425
https://www.livescores.com/ls-web-assets/js/ls.bundle-919a6747d6dd94b8fba76ed660fb3b12.js
1542
411
https://cdn-ukwest.onetrust.com/scripttemplates/6.31.0/otBannerSdk.js
9642
301
https://securepubads.g.doubleclick.net/gpt/pubads_impl_2022111001.js
945
233
https://www.livescores.com/?tz=-8
1341
201
https://www.googletagmanager.com/gtm.js?id=GTM-MGW6C35
5807
180
https://www.livescores.com/?tz=-8
2060
137
https://www.googletagservices.com/tag/js/gpt.js
4860
132
https://www.googletagmanager.com/gtm.js?id=GTM-MGW6C35
5610
115
https://www.googletagmanager.com/gtm.js?id=GTM-MGW6C35
1242
99
https://www.googletagservices.com/tag/js/gpt.js
708
97
https://www.googletagmanager.com/gtm.js?id=GTM-MGW6C35
855
90
https://www.googletagmanager.com/gtm.js?id=GTM-MGW6C35
5725
82
https://www.livescores.com/ls-web-assets/js/ls.bundle-919a6747d6dd94b8fba76ed660fb3b12.js
5987
82
https://www.livescores.com/?tz=-8
630
74
https://js-sec.indexww.com/ht/p/188832-82910719724410.js
7449
74
https://www.livescores.com/?tz=-8
1953
62
https://www.google-analytics.com/analytics.js
6257
59
https://www.google-analytics.com/analytics.js
1184
58
Avoid non-composited animations — 1 animated element found
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Element Name
Image elements have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of livescores.com on mobile screens.
Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.

Budgets

Performance budget
It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.
Timing budget
It is advised to set a timing budget to monitor the performance of your site.

Audits

Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://livescores.com/
http/1.1
0
116.29799986258
404
0
301
text/html
https://www.livescores.com/
h2
116.67599994689
130.5159998592
22605
206509
200
text/html
Document
https://fonts.googleapis.com/css2?family=Roboto:wght@400;700&display=swap
h2
148.90699996613
163.0919999443
1467
5292
200
text/css
Stylesheet
https://www.livescores.com/ls-web-assets/js/ls.bundle-919a6747d6dd94b8fba76ed660fb3b12.js
h2
149.11199989729
162.68599987961
10036
27624
200
application/javascript
Script
https://www.livescores.com/_next/static/css/1184e4c1cc17d22bf0e7.css
h2
149.30399996229
156.4879999496
1320
2266
200
text/css
Stylesheet
https://www.livescores.com/_next/static/css/69d813229c3e3dc60fe0.css
h2
149.64900002815
271.56899985857
4785
14799
200
text/css
Stylesheet
https://www.livescores.com/_next/static/css/00bbbe9968a2b5ba69a3.css
h2
150.08999989368
188.57500003651
5285
20327
200
text/css
Stylesheet
https://cdn3.livescore.com/web2/img/fb_like_disabled.png
h2
170.87700008415
206.10200008377
2244
1447
200
image/png
Image
https://www.googletagmanager.com/gtm.js?id=GTM-MGW6C35
h2
171.11100000329
186.8709998671
61122
172664
200
application/javascript
Script
https://www.googletagservices.com/tag/js/gpt.js
h2
171.27100005746
178.86999994516
28173
80579
200
text/javascript
Script
https://securepubads.g.doubleclick.net/gpt/pubads_impl_2022111001.js
h2
208.17700005136
217.67099993303
133318
391651
200
text/javascript
Script
https://securepubads.g.doubleclick.net/pagead/ppub_config?ippd=www.livescores.com
h2
211.81300003082
218.82899990305
1052
194
200
application/json
XHR
https://www.google-analytics.com/analytics.js
h2
259.30899986997
265.432999935
20664
50230
200
text/javascript
Script
https://geo.livescore.com/me/
h2
330.77599992976
432.49300005846
291
19
200
application/javascript
Script
https://www.google-analytics.com/plugins/ua/linkid.js
h2
338.80000002682
343.1209998671
1678
1569
200
text/javascript
Script
https://www.livescores.com/ls-web-assets/images/ls_header@2x-306292c9dad310aba03909053040d5c6.jpg
h2
374.70899987966
418.7980000861
44819
44029
200
image/jpeg
Image
data
404.77399993688
404.9169998616
0
468
200
image/svg+xml
Image
https://www.livescores.com/ls-web-assets/svgs/common/warning-859eac02650c539cd8dd5acbd39ceaef.svg
h2
498.91499988735
504.24899999052
1236
696
200
image/svg+xml
Image
https://www.livescores.com/ls-web-assets/svgs/common/toggle-50e0f9b80491c1e5135b9836442c308b.svg
h2
501.215999946
507.05099990591
1098
424
200
image/svg+xml
Image
https://www.livescores.com/ls-web-assets/svgs/common/cristianoRonaldo-b52670bcc6431c5e45c4ce4c5c4befb4.svg
h2
501.81000004523
506.6410000436
4846
11004
200
image/svg+xml
Image
https://www.google-analytics.com/j/collect?v=1&_v=j98&a=1888436466&t=pageview&_s=1&dl=https%3A%2F%2Fwww.livescores.com%2F&ul=en-us&de=UTF-8&dt=Soccer%20Live%20Scores%20-%20powered%20by%20LiveScore.com&sd=24-bit&sr=360x640&vp=952x1692&je=0&_u=aGBACEAjBAAAACAEK~&jid=486277929&gjid=1387279741&cid=1965640676.1668668290&tid=UA-121657370-1&_gid=2084543587.1668668290&_r=1&gtm=2wgb90MGW6C35&cd2=2022-11-16T22%3A58%3A10.282-08%3A00&cd3=1668668290282.xqissqiw&cd5=GTM-MGW6C35&cd6=&cd7=TYPE_NAVIGATE&cd8=0&cd13=Mozilla%2F5.0%20(Linux%3B%20Android%207.0%3B%20Moto%20G%20(4))%20AppleWebKit%2F537.36%20(KHTML%2C%20like%20Gecko)%20Chrome%2F98.0.4695.0%20Mobile%20Safari%2F537.36%20Chrome-Lighthouse&cd15=https%3A%2F%2Fwww.livescores.com%2F&cd17=GTM-MGW6C35_68&cd1=1965640676.1668668290&cd4=pageview&z=955692658
h2
517.02799997292
521.58900001086
617
2
200
text/plain
XHR
https://stats.g.doubleclick.net/j/collect?t=dc&aip=1&_r=3&v=1&_v=j98&tid=UA-121657370-1&cid=1965640676.1668668290&jid=486277929&gjid=1387279741&_gid=2084543587.1668668290&_u=aGBACEAiBAAAACAEK~&z=973079784
h2
539.58599991165
543.55499986559
690
2
200
text/plain
XHR
https://www.google.com/ads/ga-audiences?t=sr&aip=1&_r=4&slf_rd=1&v=1&_v=j98&tid=UA-121657370-1&cid=1965640676.1668668290&jid=486277929&_u=aGBACEAiBAAAACAEK~&z=1069269166
h2
548.87400008738
558.85199992917
673
42
200
image/gif
Image
https://www.livescores.com/
h2
1013.6929999571
1108.467000071
435
0
200
text/html
XHR
https://www.livescores.com/?tz=-8
h2
1112.0050000027
1134.1969999485
23544
188569
200
text/html
Document
https://fonts.googleapis.com/css2?family=Roboto:wght@400;700&display=swap
h2
1147.9319999926
1148.0890000239
1467
5292
200
text/css
Stylesheet
https://www.livescores.com/ls-web-assets/js/ls.bundle-919a6747d6dd94b8fba76ed660fb3b12.js
h2
1148.2160000596
1148.3680000529
10036
27624
200
application/javascript
Script
https://www.livescores.com/_next/static/css/1184e4c1cc17d22bf0e7.css
h2
1148.4469999559
1148.5579998698
1320
2266
200
text/css
Stylesheet
https://www.livescores.com/_next/static/css/69d813229c3e3dc60fe0.css
h2
1148.6909999512
1148.7970000599
4785
14799
200
text/css
Stylesheet
https://www.livescores.com/_next/static/css/00bbbe9968a2b5ba69a3.css
h2
1148.9909999073
1149.1219999734
5285
20327
200
text/css
Stylesheet
https://cdn3.livescore.com/web2/img/fb_like_disabled.png
h2
1149.2540000472
1149.3740000296
2244
1447
200
image/png
Image
https://www.googletagmanager.com/gtm.js?id=GTM-MGW6C35
h2
1154.5770000666
1154.7860000283
61122
172664
200
application/javascript
Script
https://www.googletagservices.com/tag/js/gpt.js
h2
1155.2269998938
1155.4109998979
28173
80579
200
text/javascript
Script
https://geo.livescore.com/me/
h2
1161.0149999615
1258.942999877
291
19
200
application/javascript
Script
https://www.livescores.com/ls-web-assets/images/ls_header@2x-306292c9dad310aba03909053040d5c6.jpg
h2
1161.0489999875
1161.1800000537
44819
44029
200
image/jpeg
Image
https://securepubads.g.doubleclick.net/gpt/pubads_impl_2022111001.js
h2
1220.2800000086
1220.5379998777
133318
391651
200
text/javascript
Script
https://securepubads.g.doubleclick.net/pagead/ppub_config?ippd=www.livescores.com
h2
1224.5169999078
1230.4239999503
1052
194
200
application/json
XHR
https://www.google-analytics.com/analytics.js
h2
1247.6389999501
1247.9949998669
20664
50230
200
text/javascript
Script
https://www.google-analytics.com/plugins/ua/linkid.js
h2
1382.8990000766
1383.2499999553
1678
1569
200
text/javascript
Script
https://www.livescores.com/ls-web-assets/svgs/common/warning-859eac02650c539cd8dd5acbd39ceaef.svg
h2
1426.1109998915
1426.335999975
1236
696
200
image/svg+xml
Image
https://www.livescores.com/ls-web-assets/svgs/common/toggle-50e0f9b80491c1e5135b9836442c308b.svg
h2
1431.9869999308
1432.2079999838
1098
424
200
image/svg+xml
Image
https://www.livescores.com/ls-web-assets/svgs/common/cristianoRonaldo-b52670bcc6431c5e45c4ce4c5c4befb4.svg
h2
1432.5729999691
1432.6889999211
4846
11004
200
image/svg+xml
Image
data
1443.3539998718
1443.4690000489
0
468
200
image/svg+xml
Image
https://www.google-analytics.com/collect?v=1&_v=j98&a=224403502&t=pageview&_s=1&dl=https%3A%2F%2Fwww.livescores.com%2F%3Ftz%3D-8&ul=en-us&de=UTF-8&dt=Soccer%20Live%20Scores%20-%20powered%20by%20LiveScore.com&sd=24-bit&sr=360x640&vp=952x1692&je=0&_u=SCCACEAjBAAAAAAEK~&jid=&gjid=&cid=1965640676.1668668290&tid=UA-121657370-1&_gid=2084543587.1668668290&gtm=2wgb90MGW6C35&cd2=2022-11-16T22%3A58%3A11.272-08%3A00&cd3=1668668291272.5ho70wlc&cd5=GTM-MGW6C35&cd6=https%3A%2F%2Fwww.livescores.com%2F&cd7=TYPE_NAVIGATE&cd8=0&cd13=Mozilla%2F5.0%20(Linux%3B%20Android%207.0%3B%20Moto%20G%20(4))%20AppleWebKit%2F537.36%20(KHTML%2C%20like%20Gecko)%20Chrome%2F98.0.4695.0%20Mobile%20Safari%2F537.36%20Chrome-Lighthouse&cd15=https%3A%2F%2Fwww.livescores.com%2F%3Ftz%3D-8&cd17=GTM-MGW6C35_68&cd1=1965640676.1668668290&cd4=pageview&z=1253111116
h2
1471.2829999626
1477.5159999263
597
35
200
image/gif
Image
https://www.livescores.com/ls-web-assets/svgs/common/pen-c123be2d2cddf58c8a19666c56baa302.svg
h2
1540.1409999467
1544.4789999165
1344
849
200
image/svg+xml
Image
https://www.livescores.com/?tz=-8
h2
1945.0910000596
1958.3600000478
467
0
200
text/html
XHR
https://cdn-ukwest.onetrust.com/scripttemplates/otSDKStub.js
h2
1960.6069999281
1998.5909999814
8044
21748
200
application/javascript
Script
https://js-sec.indexww.com/ht/p/188832-82910719724410.js
h2
1961.086000083
2137.3119999189
42559
146502
200
text/javascript
Script
https://cdn-ukwest.onetrust.com/consent/55d519ea-ef26-44f4-843d-07646ab5eb8d/55d519ea-ef26-44f4-843d-07646ab5eb8d.json
h2
2007.4859999586
2042.4780000467
2230
3130
200
application/x-javascript
XHR
https://geolocation.onetrust.com/cookieconsentpub/v1/geo/location
h2
2046.2120000739
2076.2239999603
465
75
200
application/json
XHR
https://cdn-ukwest.onetrust.com/scripttemplates/6.31.0/otBannerSdk.js
h2
2088.8149999082
2147.4359999411
81849
342379
200
application/javascript
Script
https://match.adsrvr.org/track/rid?ttd_pid=casale&fmt=json&p=188832&gdpr=1
h2
2163.932000054
2181.3129999209
518
63
200
application/json
XHR
https://cdn-ukwest.onetrust.com/consent/55d519ea-ef26-44f4-843d-07646ab5eb8d/16aaaff8-4c8c-4fe9-a68a-1bf23e7e7e8f/en.json
h2
2197.5390000734
2255.1349999849
30593
175232
200
application/x-javascript
Fetch
https://cdn-ukwest.onetrust.com/vendorlist/iab2Data.json
h2
2198.2149998657
2264.9979998823
53664
369825
200
application/x-javascript
Fetch
https://cdn-ukwest.onetrust.com/scripttemplates/6.31.0/otTCF.js
h2
2199.6669999789
2250.1719999127
15846
69319
200
application/javascript
Script
https://api.rlcdn.com/api/identity?pid=2&rt=envelope&cv=CPimpMrPimpMrAcABBENCqCgAAAAAH_AAChQAAARrAJMNW4gC7MscGbaMIoEQIwrCQ6gUAFFAMLRAYQOrgp2VwE-sIEACAUATgRAhwBRgwCAAASAJCIgJAjwQCAAiAQAAgAVCIQAEbAILACwMAgAFANCxAigCECQgyIAIpTAgKAACAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAUAEEABAEaAA.YAAAD_gAAAAA&ct=4
h2
2406.5219999757
2444.3169999868
426
0
204
text/plain
XHR
https://cdn-ukwest.onetrust.com/scripttemplates/6.31.0/assets/otFlat.json
h2
2433.9429999236
2494.7019999381
3846
12867
200
application/json
Fetch
https://cdn-ukwest.onetrust.com/scripttemplates/6.31.0/assets/v2/otPcCenter.json
h2
2434.5960000064
2472.1490000375
12446
48587
200
application/json
Fetch
https://cdn-ukwest.onetrust.com/scripttemplates/6.31.0/assets/otCookieSettingsButton.json
h2
2435.1629999001
2471.4219998568
2667
4753
200
application/json
Fetch
https://cdn-ukwest.onetrust.com/scripttemplates/6.31.0/assets/otCommonStyles.css
h2
2435.8149999753
2484.3830000609
5021
21289
200
text/css
Fetch
https://fonts.gstatic.com/s/roboto/v30/KFOlCnqEu92Fr1MmWUlfBBc4AMP6lQ.woff2
h2
2532.5029999949
2535.7439999934
11967
11040
200
font/woff2
Font
https://fonts.gstatic.com/s/roboto/v30/KFOmCnqEu92Fr1Mu4mxKKTU1Kg.woff2
h2
2533.6559999269
2537.7100000624
11956
11028
200
font/woff2
Font
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
-975.108
18.601
-943.817
5.063
-922.845
24.162
-883.144
12.506
-870.6
22.462
-844.474
58.299
-775.87
29.249
-745.588
9.985
-734.68
24.817
-709.537
100.582
-608.656
6.659
-601.899
9.017
-591.644
6.908
-573.023
8.416
-102.55
102.708
27.056
15.442
42.798
9.01
57.37
28.765
86.157
33.074
120.8
20.572
141.936
106.157
248.11
5.579
255.293
7.498
262.829
29.355
293.286
11.158
306.921
44.903
352.254
8.503
361.164
68.591
445.047
5.321
831.555
20.545
891.205
6.151
966.911
11.789
1035.389
18.594
1076.51
12.984
1145.321
7.83
1157.822
6.906
1164.768
161.262
1386.602
150.298
1543.722
5.384
1549.356
9.97
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Metrics

First Contentful Paint — 2.5 s
The time taken for the first image or text on the page to be rendered.
Speed Index — 3.8 s
The time taken for the page contents to be visibly populated.

Audits

First Meaningful Paint — 3.5 s
The time taken for the primary content of the page to be rendered.

Other

Eliminate render-blocking resources — Potential savings of 150 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Livescores.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://fonts.googleapis.com/css2?family=Roboto:wght@400;700&display=swap
1467
150
Serve static assets with an efficient cache policy — 10 resources found
Livescores.com can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
https://geo.livescore.com/me/
0
291
https://geo.livescore.com/me/
0
291
https://www.google-analytics.com/plugins/ua/linkid.js
3600000
1678
https://www.google-analytics.com/plugins/ua/linkid.js
3600000
1678
https://www.google-analytics.com/analytics.js
7200000
20664
https://www.google-analytics.com/analytics.js
7200000
20664
https://js-sec.indexww.com/ht/p/188832-82910719724410.js
14400000
42559
https://cdn-ukwest.onetrust.com/scripttemplates/6.31.0/otBannerSdk.js
86400000
81849
https://cdn-ukwest.onetrust.com/scripttemplates/6.31.0/otTCF.js
86400000
15846
https://cdn-ukwest.onetrust.com/scripttemplates/otSDKStub.js
86400000
8044
Reduce JavaScript execution time — 3.2 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://www.livescores.com/?tz=-8
1894.592
29.036
16.428
https://js-sec.indexww.com/ht/p/188832-82910719724410.js
734.136
579.308
8.904
https://securepubads.g.doubleclick.net/gpt/pubads_impl_2022111001.js
660.076
461.524
197.272
https://cdn-ukwest.onetrust.com/scripttemplates/6.31.0/otBannerSdk.js
656.24
363.404
33.14
https://www.livescores.com/ls-web-assets/js/ls.bundle-919a6747d6dd94b8fba76ed660fb3b12.js
534.496
523.32
10.224
https://www.googletagmanager.com/gtm.js?id=GTM-MGW6C35
403.772
317.036
72.776
Unattributable
364.712
15.648
0
https://www.googletagservices.com/tag/js/gpt.js
264.068
214.02
39.284
https://www.google-analytics.com/analytics.js
256.764
141.532
27.504
https://www.livescores.com/
127.252
10.484
7.86
https://cdn-ukwest.onetrust.com/scripttemplates/otSDKStub.js
82.804
67.452
6.472
https://www.google-analytics.com/plugins/ua/linkid.js
76.544
73.032
1.8

Metrics

Time to Interactive — 9.6 s
The time taken for the page to become fully interactive.
Total Blocking Time — 1,320 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).
Largest Contentful Paint — 5.7 s
The timing of the largest text or image that is painted.

Audits

Max Potential First Input Delay — 650 ms
Users could experience a delay when interacting with the page.

Other

Reduce unused JavaScript — Potential savings of 179 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://securepubads.g.doubleclick.net/gpt/pubads_impl_2022111001.js
133318
97821
https://cdn-ukwest.onetrust.com/scripttemplates/6.31.0/otBannerSdk.js
81849
36894
https://www.googletagmanager.com/gtm.js?id=GTM-MGW6C35
61122
25857
https://js-sec.indexww.com/ht/p/188832-82910719724410.js
42559
22556
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
Avoid multiple page redirects — Potential savings of 6,070 ms
Redirects can cause additional delays before the page can begin loading. Livescores.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://livescores.com/
3510
https://www.livescores.com/
2559
https://www.livescores.com/?tz=-8
0
Avoid an excessive DOM size — 3,404 elements
A large DOM (Document Object Model) will increase memory usage, cause longer system calculations as well as costly layout reflows.
Statistic Element Value
Total DOM Elements
3404
Maximum DOM Depth
15
Maximum Child Elements
179
Minimize main-thread work — 6.1 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Script Evaluation
2825.352
Style & Layout
904.824
Other
895.116
Rendering
597.496
Script Parsing & Compilation
427.044
Parse HTML & CSS
275.884
Garbage Collection
182.732
Reduce the impact of third-party code — Third-party code blocked the main thread for 1,270 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Transfer Size (Bytes) Main-Thread Blocking Time (Ms)
42559
488.464
325776
469.168
216671
209.14
122244
70.416
45898
29.544
26857
0
673
0
518
0
426
0
Largest Contentful Paint image was lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Element
First Contentful Paint (3G) — 4890 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.
90

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of livescores.com. This includes details about various page attributes that can be optimized.

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
Heading elements appear in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`button`, `link`, and `menuitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
ARIA `meter` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `progressbar` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
ARIA `tooltip` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `treeitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.
Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Names and labels

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Links have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.
`<object>` elements have alternate text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Internationalization and localization

`<html>` element has a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Livescores.com may provide assistance to deaf or hearing-impaired users with captions on videos.

Names and labels

Buttons do not have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Failing Elements

Contrast

Background and foreground colors do not have a sufficient contrast ratio.
Many (if not most) users find low-contrast text difficult or impossible to read.
Failing Elements

Manual Checks

The page has a logical tab order
The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.
Interactive controls are keyboard focusable
Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.
Interactive elements indicate their purpose and state
Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.
The user's focus is directed to new content added to the page
When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.
User focus is not accidentally trapped in a region
Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.
Custom controls have associated labels
Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.
Custom controls have ARIA roles
Ensure that all custom interactive controls have appropriate ARIA roles.
Visual order on the page follows DOM order
Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.
Offscreen content is hidden from assistive technology
Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.
HTML5 landmark elements are used to improve navigation
Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.
75

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that livescores.com should incorporate. This includes practices such as protecting pages with HTTPS.

Audits

Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids front-end JavaScript libraries with known security vulnerabilities
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).
Description Directive Severity
No CSP found in enforcement mode
High

Audits

Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.
Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

Audits

Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Properly defines charset
It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL Request Resolution
http://livescores.com/
Allowed

Audits

Serves images with low resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
URL Displayed size Actual size Expected size
https://cdn3.livescore.com/web2/img/fb_like_disabled.png
94 x 20
96 x 20
188 x 40

Audits

Uses deprecated APIs — 2 warnings found
Avoid deprecated APIs which will eventually be removed the browser.
Deprecation / Warning Source
Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to the end user’s experience. For more help, check https://xhr.spec.whatwg.org/.
Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to the end user’s experience. For more help, check https://xhr.spec.whatwg.org/.
96

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for livescores.com. This includes optimizations such as providing meta data.

Mobile Friendly

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of livescores.com on mobile screens.
Document uses legible font sizes — 75.28% legible text
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Source Selector % of Page Text Font Size
.ch
1.58%
11px
.gf
1.25%
11px
.pb
1.16%
11px
20.73%
< 12px
75.28%
≥ 12px

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Document has a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the content.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Links are crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Mobile Friendly

Tap targets are not sized appropriately — 45% appropriately sized tap targets
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.
Tap Target Size Overlapping Target
116x20
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
USA
USA
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
130x27
74x33
74x33
74x33
74x33
74x33
74x33
74x33

Manual Checks

Structured data is valid
Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
50

PWA

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of livescores.com. This includes details about web app manifests.

Installable

Web app manifest and service worker meet the installability requirements
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.

PWA Optimized

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of livescores.com on mobile screens.
Provides a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.

PWA Optimized

Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Content is not sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.
Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.
Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.
Hosting

Server Location

Server IP Address: 34.111.30.205
Continent:
Country:
Region:
City:
Longitude:
Latitude:
Currencies:
Languages:

Web Hosting Provider

Name IP Address
Google LLC
Registration

Domain Registrant

Private Registration: No
Name: Livescore Limited
Organization: Livescore Limited
Country: GI
City: Gibraltar
State:
Post Code: GX11 1AA
Email: hostmaster@anzogroup.com
Phone: +44.2074788137
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Name IP Address
CSC CORPORATE DOMAINS, INC. 204.74.99.103
Security

Visitor Safety

Mature Content: Not Likely
McAfee WebAdvisor Rating: Unknown
WOT Rating:
WOT Trustworthiness: 95/100
WOT Child Safety: 93/100
Note: Safety information is not guaranteed.

SSL/TLS Certificate

Issued To: www.livescores.com
Issued By: GTS CA 1D4
Valid From: 20th February, 2024
Valid To: 20th May, 2024
Subject: CN = www.livescores.com
Hash: b27e0c53
Issuer: CN = GTS CA 1D4
O = Google Trust Services LLC
S = US
Version: 2
Serial Number: 0xD4E2CF2214693BCF092AEC5CF851527E
Serial Number (Hex): D4E2CF2214693BCF092AEC5CF851527E
Valid From: 20th February, 2024
Valid To: 20th May, 2024
Signature Algorithm (Short Name): RSA-SHA256
Signature Algorithm (Long Name): sha256WithRSAEncryption
Authority Key Identifier: keyid:25:E2:18:0E:B2:57:91:94:2A:E5:D4:5D:86:90:83:DE:53:B3:B8:92
Extended Key Usage: TLS Web Server Authentication
CRL Distribution Points:
Full Name:
URI:http://crls.pki.goog/gts1d4/fn5d1TLzrUY.crl

Certificate Policies: Policy: 2.23.140.1.2.1
Policy: 1.3.6.1.4.1.11129.2.5.3

Authority Information Access: OCSP - URI:http://ocsp.pki.goog/s/gts1d4/nOp1MO31-wM
CA Issuers - URI:http://pki.goog/repo/certs/gts1d4.der

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 76:FF:88:3F:0A:B6:FB:95:51:C2:61:CC:F5:87:BA:34:
B4:A4:CD:BB:29:DC:68:42:0A:9F:E6:67:4C:5A:3A:74
Timestamp : Feb 20 07:07:49.377 2024 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:21:00:DE:43:E2:63:F8:81:D9:23:9A:5D:C6:
FD:D0:60:D4:34:63:CC:31:CA:42:43:24:7D:8F:AC:6B:
D0:0F:C2:9E:F6:02:20:71:15:32:74:45:6B:C1:40:BC:
D1:68:66:6B:60:CD:EE:2C:05:EC:BB:94:09:5F:57:9B:
DD:CD:64:57:56:07:DA
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 48:B0:E3:6B:DA:A6:47:34:0F:E5:6A:02:FA:9D:30:EB:
1C:52:01:CB:56:DD:2C:81:D9:BB:BF:AB:39:D8:84:73
Timestamp : Feb 20 07:07:49.359 2024 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:46:02:21:00:90:3A:6C:3A:BC:32:70:2A:1F:51:D2:
BF:FD:8E:10:58:81:97:9D:C9:3D:52:61:3D:74:FD:39:
BB:9F:7F:43:2C:02:21:00:99:36:1B:87:DB:2E:DF:43:
D2:95:55:89:15:2B:9A:34:21:4A:F6:71:EB:64:30:6C:
A4:4A:E4:E2:20:83:7A:28
Key Usage: Digital Signature, Key Encipherment
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:livescores.com
DNS:www.livescores.com
Technical

DNS Lookup

A Records

Host IP Address Class TTL
livescores.com. 34.111.30.205 IN 10

NS Records

Host Nameserver Class TTL
livescores.com. ns-cloud-e1.googledomains.com. IN 21600
livescores.com. ns-cloud-e2.googledomains.com. IN 21600
livescores.com. ns-cloud-e3.googledomains.com. IN 21600
livescores.com. ns-cloud-e4.googledomains.com. IN 21600

SOA Records

Domain Name Primary NS Responsible Email TTL
livescores.com. ns-cloud-e1.googledomains.com. cloud-dns-hostmaster.google.com. 21600

TXT Records

Host Value Class TTL
livescores.com. google-site-verification=gC47eQ5gY8wLaIWZ5GjjKqapQOocu31FXynrJnGlfX8 IN 300

HTTP Response Headers

HTTP-Code: HTTP/2 200
server: openresty/1.21.4.1
date: 24th February, 2024
cache-control: public, s-maxage=60, max-age=60, stale-while-revalidate
content-type: text/html; charset=utf-8
content-length: 698267
x-cache-status: STALE
x-location-header: my specific-location header content! 10
via: 1.1 google
etag: "aa79b-kT6KfCKBs5Sne8X7/JMqstahz60"
vary: Accept-Encoding
age: 45
alt-svc: h3=":443"; ma=2592000,h3-29=":443"; ma=2592000

Whois Lookup

Created: 4th November, 1998
Changed: 30th October, 2023
Expires: 3rd November, 2024
Registrar: CSC CORPORATE DOMAINS, INC.
Status: clientTransferProhibited
Nameservers: ns-cloud-e1.googledomains.com
ns-cloud-e2.googledomains.com
ns-cloud-e3.googledomains.com
ns-cloud-e4.googledomains.com
Owner Name: Livescore Limited
Owner Organization: Livescore Limited
Owner Street: Floor 2 Suite 2 Waterport Place
Owner Post Code: GX11 1AA
Owner City: Gibraltar
Owner Country: GI
Owner Phone: +44.2074788137
Owner Email: hostmaster@anzogroup.com
Admin Name: Livescore Limited
Admin Organization: Livescore Limited
Admin Street: Floor 2 Suite 2 Waterport Place
Admin Post Code: GX11 1AA
Admin City: Gibraltar
Admin Country: GI
Admin Phone: +44.2074788137
Admin Email: hostmaster@anzogroup.com
Tech Name: Livescore Limited
Tech Organization: Livescore Limited
Tech Street: Floor 2 Suite 2 Waterport Place
Tech Post Code: GX11 1AA
Tech City: Gibraltar
Tech Country: GI
Tech Phone: +44.2074788137
Tech Email: hostmaster@anzogroup.com
Full Whois:
Domain Name: livescores.com
Registry Domain ID: 3257528_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.corporatedomains.com
Registrar URL: www.cscprotectsbrands.com
Updated Date: 2023-10-30T01:10:48Z
Creation Date: 1998-11-04T00:00:00Z
Registrar Registration Expiration Date: 2024-11-03T05:00:00Z
Registrar: CSC CORPORATE DOMAINS, INC.
Sponsoring Registrar IANA ID: 299
Registrar Abuse Contact Email: domainabuse@cscglobal.com
Registrar Abuse Contact Phone: +1.8887802723
Domain Status: clientTransferProhibited http://www.icann.org/epp#clientTransferProhibited
Registry Registrant ID:
Registrant Name: Livescore Limited
Registrant Organization: Livescore Limited
Registrant Street: Floor 2 Suite 2 Waterport Place
Registrant City: Gibraltar
Registrant State/Province:
Registrant Postal Code: GX11 1AA
Registrant Country: GI
Registrant Phone: +44.2074788137
Registrant Phone Ext:
Registrant Fax: +44.2074788137
Registrant Fax Ext:
Registrant Email: hostmaster@anzogroup.com
Registry Admin ID:
Admin Name: Livescore Limited
Admin Organization: Livescore Limited
Admin Street: Floor 2 Suite 2 Waterport Place
Admin City: Gibraltar
Admin State/Province:
Admin Postal Code: GX11 1AA
Admin Country: GI
Admin Phone: +44.2074788137
Admin Phone Ext:
Admin Fax: +44.2074788137
Admin Fax Ext:
Admin Email: hostmaster@anzogroup.com
Registry Tech ID:
Tech Name: Livescore Limited
Tech Organization: Livescore Limited
Tech Street: Floor 2 Suite 2 Waterport Place
Tech City: Gibraltar
Tech State/Province:
Tech Postal Code: GX11 1AA
Tech Country: GI
Tech Phone: +44.2074788137
Tech Phone Ext:
Tech Fax: +44.2074788137
Tech Fax Ext:
Tech Email: hostmaster@anzogroup.com
Name Server: ns-cloud-e2.googledomains.com
Name Server: ns-cloud-e4.googledomains.com
Name Server: ns-cloud-e1.googledomains.com
Name Server: ns-cloud-e3.googledomains.com
DNSSEC: unsigned
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2023-10-30T01:10:48Z <<<

For more information on Whois status codes, please visit https://icann.org/epp

Corporation Service Company(c) (CSC) The Trusted Partner of More than 50% of the 100 Best Global Brands.

Contact us to learn more about our enterprise solutions for Global Domain Name Registration and Management, Trademark Research and Watching, Brand, Logo and Auction Monitoring, as well SSL Certificate Services and DNS Hosting.

NOTICE: You are not authorized to access or query our WHOIS database through the use of high-volume, automated, electronic processes or for the purpose or purposes of using the data in any manner that violates these terms of use. The Data in the CSC WHOIS database is provided by CSC for information purposes only, and to assist persons in obtaining information about or related to a domain name registration record. CSC does not guarantee its accuracy. By submitting a WHOIS query, you agree to abide by the following terms of use: you agree that you may use this Data only for lawful purposes and that under no circumstances will you use this Data to: (1) allow, enable, or otherwise support the transmission of mass unsolicited, commercial advertising or solicitations via direct mail, e-mail, telephone, or facsimile; or (2) enable high volume, automated, electronic processes that apply to CSC (or its computer systems). CSC reserves the right to terminate your access to the WHOIS database in its sole discretion for any violations by you of these terms of use. CSC reserves the right to modify these terms at any time.

Register your domain name at http://www.cscglobal.com

Nameservers

Name IP Address
ns-cloud-e1.googledomains.com 216.239.32.110
ns-cloud-e2.googledomains.com 216.239.34.110
ns-cloud-e3.googledomains.com 216.239.36.110
ns-cloud-e4.googledomains.com 216.239.38.110
Related

Subdomains

Similar Sites

Domain Valuation Snoop Score
0/5
$957 USD 1/5
$33,019,262 USD 5/5
$7,560 USD 2/5
$246,282 USD 3/5

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
0/5
$749 USD 1/5
$10 USD
0/5

Sites hosted on the same IP address