Tools & Wizards About Us
amp.cincinnati.com screenshot

Report Summary

  • 61

    Performance

    Renders faster than
    76% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 66% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

amp.cincinnati.com

Cincinnati News, Sports and Things to Do | Cincinnati Enquirer

Page Load Speed

1.9 sec in total

First Response

227 ms

Resources Loaded

948 ms

Page Rendered

692 ms

amp.cincinnati.com screenshot

About Website

Welcome to amp.cincinnati.com homepage info - get ready to check Amp Cincinnati best content for United States right away, or after learning these important things about amp.cincinnati.com

Breaking Cincinnati news, traffic, weather and local headlines from The Cincinnati Enquirer newspaper.

Visit amp.cincinnati.com

Key Findings

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

Performance Metrics

amp.cincinnati.com performance score

61

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

13/100

10%

LCP (Largest Contentful Paint)

Value25.3 s

0/100

25%

SI (Speed Index)

Value4.7 s

69/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value4.7 s

80/100

10%

Network Requests Diagram

www.cincinnati.com

227 ms

webcomponents-loader.js

74 ms

polyfill.min.js

557 ms

gallium.js

83 ms

gallium.js

261 ms

Our browser made a total of 20 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Amp.cincinnati.com, 20% (4 requests) were made to Gannett-cdn.com and 5% (1 request) were made to Cincinnati.com. The less responsive or slowest element that took the longest time to load (557 ms) relates to the external source Polyfill-fastly.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 132.3 kB (3%)

Content Size

5.1 MB

After Optimization

5.0 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Amp.cincinnati.com main page is 5.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. 15% of websites need less resources to load. Images take 4.8 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 130.9 kB

  • Original 166.9 kB
  • After minification 166.6 kB
  • After compression 36.0 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 130.9 kB or 78% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 4.8 MB
  • After minification 4.8 MB

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

JavaScript Optimization

-1%

Potential reduce by 1.4 kB

  • Original 147.2 kB
  • After minification 147.0 kB
  • After compression 145.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.

Requests Breakdown

Number of requests can be reduced by 6 (46%)

Requests Now

13

After Optimization

7

  • AJAX
  • Images
  • JavaScript

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

Network Requests Diagram

www.cincinnati.com

www.cincinnati.com

227 ms

webcomponents-loader.js

webcomponents-loader.js

74 ms

polyfill.min.js

polyfill.min.js

557 ms

gallium.js

gallium.js

83 ms

gallium.js

gallium.js

261 ms

custom-elements-es5-adapter.js

custom-elements-es5-adapter.js

78 ms

section.js

section.js

113 ms

webcomponents-lite.js

webcomponents-lite.js

84 ms

74921542007-082324-hyde-park-revitilization-01.jpg

74921542007-082324-hyde-park-revitilization-01.jpg

80 ms

74904589007-getty-images-1149708298.jpg

74904589007-getty-images-1149708298.jpg

65 ms

74756043007-081024-bengals-pre-01.JPG

74756043007-081024-bengals-pre-01.JPG

61 ms

icon-instagram_24.png

icon-instagram_24.png

63 ms

UnifySans_W_SBd.woff

UnifySans_W_SBd.woff

34 ms

UnifySans_W_Bd.woff

UnifySans_W_Bd.woff

76 ms

UnifySans_W_Rg.woff

UnifySans_W_Rg.woff

49 ms

universal.html

universal.html

59 ms

polymer.html

polymer.html

66 ms

UnifySerif_W_Rg.woff

UnifySerif_W_Rg.woff

54 ms

UnifySerif_W_SBd.woff

UnifySerif_W_SBd.woff

42 ms

UnifySerif_W_Bd.woff

UnifySerif_W_Bd.woff

64 ms

Accessibility Review

amp.cincinnati.com accessibility score

87

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

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Definition list items are not wrapped in <dl> elements

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

Links do not have a discernible name

Best Practices

amp.cincinnati.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

amp.cincinnati.com SEO score

93

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

Mobile Friendly

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

Impact

Issue

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Amp.cincinnati.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 Amp.cincinnati.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

amp.cincinnati.com

Open Graph description is not detected on the main page of Amp Cincinnati. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: