Tools & Wizards About Us
i2.dailyrecord.co.uk screenshot

Report Summary

  • 12

    Performance

    Renders faster than
    25% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

i2.dailyrecord.co.uk

Daily Record & Sunday Mail - Scottish News, Sport, Politics and Celeb gossip

Page Load Speed

13.5 sec in total

First Response

241 ms

Resources Loaded

3.2 sec

Page Rendered

10 sec

i2.dailyrecord.co.uk screenshot

About Website

Welcome to i2.dailyrecord.co.uk homepage info - get ready to check I 2 Daily Record best content for United Kingdom right away, or after learning these important things about i2.dailyrecord.co.uk

The first for Scottish news, sport, UK and world news. Get breaking news on Scottish football teams including Rangers, Celtic FC, Hibs FC and more

Visit i2.dailyrecord.co.uk

Key Findings

We analyzed I2.dailyrecord.co.uk page load time and found that the first response time was 241 ms and then it took 13.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

i2.dailyrecord.co.uk performance score

12

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

46/100

10%

LCP (Largest Contentful Paint)

Value13.9 s

0/100

25%

SI (Speed Index)

Value13.1 s

2/100

10%

TBT (Total Blocking Time)

Value3,430 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.284

42/100

15%

TTI (Time to Interactive)

Value28.1 s

0/100

10%

Network Requests Diagram

i2.dailyrecord.co.uk

241 ms

www.dailyrecord.co.uk

159 ms

section-base.css

346 ms

chameleon-static-html-clipper.css

379 ms

marwood-extended.css

386 ms

Our browser made a total of 73 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original I2.dailyrecord.co.uk, 33% (24 requests) were made to S2-prod.dailyrecord.co.uk and 8% (6 requests) were made to S3.mirror.co.uk. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Felix.data.tm-awx.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 603.6 kB (57%)

Content Size

1.1 MB

After Optimization

449.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of I2.dailyrecord.co.uk main page is 1.1 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. HTML takes 667.7 kB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 573.2 kB

  • Original 667.7 kB
  • After minification 666.9 kB
  • After compression 94.5 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 573.2 kB or 86% of the original size.

Image Optimization

-10%

Potential reduce by 6.8 kB

  • Original 66.8 kB
  • After minification 60.1 kB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. I 2 Daily Record images are well optimized though.

JavaScript Optimization

-8%

Potential reduce by 22.3 kB

  • Original 270.1 kB
  • After minification 270.1 kB
  • After compression 247.8 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. This website has mostly compressed JavaScripts.

CSS Optimization

-3%

Potential reduce by 1.3 kB

  • Original 48.4 kB
  • After minification 48.3 kB
  • After compression 47.1 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. I2.dailyrecord.co.uk has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 45 (69%)

Requests Now

65

After Optimization

20

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

i2.dailyrecord.co.uk

i2.dailyrecord.co.uk

241 ms

www.dailyrecord.co.uk

www.dailyrecord.co.uk

159 ms

section-base.css

section-base.css

346 ms

chameleon-static-html-clipper.css

chameleon-static-html-clipper.css

379 ms

marwood-extended.css

marwood-extended.css

386 ms

brand-extended-clipper.ef152f2229c951e0.css

brand-extended-clipper.ef152f2229c951e0.css

375 ms

css2

css2

511 ms

bf9ae724b717d2d97334500c32b7d48937ddefa9f5faca2fcf2a791d702e7281

bf9ae724b717d2d97334500c32b7d48937ddefa9f5faca2fcf2a791d702e7281

940 ms

s.min.js

s.min.js

361 ms

runForceReconsent.min.js

runForceReconsent.min.js

839 ms

gpt.js

gpt.js

889 ms

iasPET.1.js

iasPET.1.js

845 ms

tags.min.js

tags.min.js

838 ms

chartbeat_mab.js

chartbeat_mab.js

843 ms

pug-runtime.min.js

pug-runtime.min.js

806 ms

section.min.js

section.min.js

814 ms

section.min.js

section.min.js

783 ms

partner.min.js

partner.min.js

783 ms

chameleon-static-html-clipper.min.js

chameleon-static-html-clipper.min.js

790 ms

withnail.min.js

withnail.min.js

805 ms

ats.js

ats.js

791 ms

felix.min.js

felix.min.js

1277 ms

style.css

style.css

853 ms

index.js

index.js

852 ms

auth-ui.min.js

auth-ui.min.js

857 ms

analytics.js.gz

analytics.js.gz

790 ms

gtm.js

gtm.js

714 ms

186772-170849978518354.js

186772-170849978518354.js

929 ms

apstag.js

apstag.js

515 ms

transparent.png

transparent.png

378 ms

transparent-wide.png

transparent-wide.png

444 ms

analytics.config.json

analytics.config.json

1018 ms

logo-dailyrecord.4c4d88d32bde1410.png

logo-dailyrecord.4c4d88d32bde1410.png

245 ms

logo-dailyrecord.png

logo-dailyrecord.png

244 ms

section.css

section.css

103 ms

withnail.css

withnail.css

158 ms

section.css

section.css

152 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4nY1M2xYkS.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4nY1M2xYkS.ttf

245 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1y4nY1M2xYkS.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1y4nY1M2xYkS.ttf

518 ms

icomoon.297eaf3448df4f03.woff

icomoon.297eaf3448df4f03.woff

115 ms

E21x_cfngu7HiRpPX3ZpNE4kY5zKSPmJXkF0VDD2RApATL3st9hiuXK_.ttf

E21x_cfngu7HiRpPX3ZpNE4kY5zKSPmJXkF0VDD2RApATL3st9hiuXK_.ttf

579 ms

E21x_cfngu7HiRpPX3ZpNE4kY5zKSPmJXkF0VDD2RAqnS73st9hiuXK_.ttf

E21x_cfngu7HiRpPX3ZpNE4kY5zKSPmJXkF0VDD2RAqnS73st9hiuXK_.ttf

703 ms

pubads_impl_2022092601.js

pubads_impl_2022092601.js

156 ms

ppub_config

ppub_config

427 ms

css2

css2

369 ms

ipso.a49db49dfe703ca7.svg

ipso.a49db49dfe703ca7.svg

376 ms

trust-project.8b902581bcc08204.svg

trust-project.8b902581bcc08204.svg

331 ms

door.js

door.js

487 ms

verify-2.0.1.min.js

verify-2.0.1.min.js

486 ms

js

js

207 ms

publishertag.js

publishertag.js

239 ms

rid

rid

466 ms

analytics.js

analytics.js

94 ms

syncframe

syncframe

211 ms

verify-2.0.1.min.css

verify-2.0.1.min.css

80 ms

icon

icon

147 ms

widgetHomepage.js

widgetHomepage.js

197 ms

tag.min.js

tag.min.js

193 ms

adsm.macro.7b4cd01e-58e4-4d3c-b14d-9c15d2911c60.js

adsm.macro.7b4cd01e-58e4-4d3c-b14d-9c15d2911c60.js

210 ms

static.min.js

static.min.js

212 ms

collect

collect

123 ms

collect

collect

233 ms

iya.css

iya.css

15 ms

iya-dailyrecord.css

iya-dailyrecord.css

45 ms

container-polyfills.js

container-polyfills.js

161 ms

iya-test-bkg.jpg

iya-test-bkg.jpg

104 ms

default.gif

default.gif

103 ms

logo-InYourArea.svg

logo-InYourArea.svg

105 ms

mirrorcouk.min.js

mirrorcouk.min.js

65 ms

%2F

%2F

193 ms

www.dailyrecord.co.uk

www.dailyrecord.co.uk

174 ms

reach-beacon.min.js

reach-beacon.min.js

170 ms

ga-audiences

ga-audiences

257 ms

Accessibility Review

i2.dailyrecord.co.uk accessibility score

81

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

i2.dailyrecord.co.uk best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

i2.dailyrecord.co.uk SEO score

82

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

Content Best Practices

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

Impact

Issue

High

Image elements do not have [alt] attributes

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise I2.dailyrecord.co.uk can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that I2.dailyrecord.co.uk main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

i2.dailyrecord.co.uk

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