Tools & Wizards About Us
nottinghampost.com screenshot

Report Summary

  • 10

    Performance

    Renders faster than
    23% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

nottinghampost.com

Nottinghamshire Live - Latest local news, sport & business from Nottingham

Page Load Speed

5.9 sec in total

First Response

146 ms

Resources Loaded

3 sec

Page Rendered

2.8 sec

nottinghampost.com screenshot

About Website

Click here to check amazing Nottingham Post content for United Kingdom. Otherwise, check out these important facts you probably never knew about nottinghampost.com

Latest news, sport and events from Nottingham. With comment, live blogs, pictures and video from the Nottinghamshire Live team, formerly the Nottingham Post.

Visit nottinghampost.com

Key Findings

We analyzed Nottinghampost.com page load time and found that the first response time was 146 ms and then it took 5.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

nottinghampost.com performance score

10

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

40/100

10%

LCP (Largest Contentful Paint)

Value14.3 s

0/100

25%

SI (Speed Index)

Value13.5 s

2/100

10%

TBT (Total Blocking Time)

Value3,770 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.324

35/100

15%

TTI (Time to Interactive)

Value33.5 s

0/100

10%

Network Requests Diagram

nottinghampost.com

146 ms

www.nottinghampost.com

44 ms

choice.js

470 ms

section-base.css

1075 ms

chameleon-static-html.css

87 ms

Our browser made a total of 62 requests to load all elements on the main page. We found that 8% of them (5 requests) were addressed to the original Nottinghampost.com, 44% (27 requests) were made to S2-prod.nottinghampost.com and 16% (10 requests) were made to I2-prod.bristolpost.co.uk. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source S2-prod.nottinghampost.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 925.8 kB (39%)

Content Size

2.4 MB

After Optimization

1.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Nottinghampost.com main page is 2.4 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 65% of websites need less resources to load. Javascripts take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 873.6 kB

  • Original 1.0 MB
  • After minification 1.0 MB
  • After compression 154.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 873.6 kB or 85% of the original size.

Image Optimization

-42%

Potential reduce by 32.9 kB

  • Original 78.2 kB
  • After minification 45.4 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. Obviously, Nottingham Post needs image optimization as it can save up to 32.9 kB or 42% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-2%

Potential reduce by 18.3 kB

  • Original 1.2 MB
  • After minification 1.2 MB
  • After compression 1.2 MB

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

-2%

Potential reduce by 1.0 kB

  • Original 47.0 kB
  • After minification 47.0 kB
  • After compression 46.0 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. Nottinghampost.com has all CSS files already compressed.

Requests Breakdown

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

Requests Now

55

After Optimization

21

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

nottinghampost.com

nottinghampost.com

146 ms

www.nottinghampost.com

www.nottinghampost.com

44 ms

choice.js

choice.js

470 ms

section-base.css

section-base.css

1075 ms

chameleon-static-html.css

chameleon-static-html.css

87 ms

marwood-extended.css

marwood-extended.css

92 ms

brand-extended-clipper.94486e3cb64858c8.css

brand-extended-clipper.94486e3cb64858c8.css

84 ms

css2

css2

80 ms

97cb40ea2af7e780a18c4c3073ee12c433061d71d5d929f444371d87670c9c77

97cb40ea2af7e780a18c4c3073ee12c433061d71d5d929f444371d87670c9c77

99 ms

s.min.js

s.min.js

93 ms

runForceReconsent.min.js

runForceReconsent.min.js

83 ms

iasPET.1.js

iasPET.1.js

89 ms

prebid-test.js

prebid-test.js

96 ms

tags.min.js

tags.min.js

93 ms

chartbeat_mab.js

chartbeat_mab.js

86 ms

section.min.js

section.min.js

1280 ms

partner.min.js

partner.min.js

85 ms

chameleon-static-html.min.js

chameleon-static-html.min.js

89 ms

section.min.js

section.min.js

1029 ms

withnail.min.js

withnail.min.js

90 ms

smile-web.min.js

smile-web.min.js

86 ms

style.css

style.css

92 ms

index.js

index.js

91 ms

auth-ui.min.js

auth-ui.min.js

95 ms

analytics.js.gz

analytics.js.gz

84 ms

ebx.js

ebx.js

100 ms

cmp2-polyfilled.js

cmp2-polyfilled.js

4 ms

gtm.js

gtm.js

235 ms

apstag.js

apstag.js

247 ms

transparent.png

transparent.png

178 ms

transparent-wide.png

transparent-wide.png

185 ms

analytics.config.json

analytics.config.json

577 ms

0_NottinghamshireLive-3.png

0_NottinghamshireLive-3.png

225 ms

logo-nottinghampost.png

logo-nottinghampost.png

107 ms

outside-black.svg

outside-black.svg

107 ms

section.css

section.css

388 ms

withnail.css

withnail.css

56 ms

section.css

section.css

476 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4n.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4n.ttf

152 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1y4n.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1y4n.ttf

171 ms

icomoon.00495dd3fc67aad5.woff

icomoon.00495dd3fc67aad5.woff

15 ms

E21x_cfngu7HiRpPX3ZpNE4kY5zKSPmJXkF0VDD2RApATL3s.ttf

E21x_cfngu7HiRpPX3ZpNE4kY5zKSPmJXkF0VDD2RApATL3s.ttf

360 ms

E21x_cfngu7HiRpPX3ZpNE4kY5zKSPmJXkF0VDD2RAqnS73s.ttf

E21x_cfngu7HiRpPX3ZpNE4kY5zKSPmJXkF0VDD2RAqnS73s.ttf

197 ms

ipso.a49db49dfe703ca7.svg

ipso.a49db49dfe703ca7.svg

6 ms

trust-project.8b902581bcc08204.svg

trust-project.8b902581bcc08204.svg

4 ms

css2

css2

18 ms

du_council_totalizer_24.min.js

du_council_totalizer_24.min.js

217 ms

prebid.js

prebid.js

255 ms

tag

tag

192 ms

0_Vistaprint.png

0_Vistaprint.png

349 ms

0_Vodafone.png

0_Vodafone.png

270 ms

0_Wayfair.png

0_Wayfair.png

133 ms

0_Watch-Shop.png

0_Watch-Shop.png

267 ms

0_Waitrose.png

0_Waitrose.png

270 ms

0_Zip-car.png

0_Zip-car.png

268 ms

0_Wickes.png

0_Wickes.png

344 ms

0_zalando.png

0_zalando.png

482 ms

0_Wilko.png

0_Wilko.png

483 ms

0_SportsDirect-Logo.png

0_SportsDirect-Logo.png

489 ms

icon-nottinghampost.f664834cac8fd646.svg

icon-nottinghampost.f664834cac8fd646.svg

6 ms

X2JS.min.js

X2JS.min.js

694 ms

ads.js

ads.js

8 ms

Accessibility Review

nottinghampost.com accessibility score

85

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

Names and labels

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

Impact

Issue

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

nottinghampost.com 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

Missing source maps for large first-party JavaScript

SEO Factors

nottinghampost.com SEO score

85

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 Nottinghampost.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Nottinghampost.com main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

nottinghampost.com

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