Tools & Wizards About Us
wews.com screenshot

Report Summary

  • 11

    Performance

    Renders faster than
    24% 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

  • 83

    SEO

    Google-friendlier than
    46% of websites

wews.com

News 5 Cleveland WEWS

Page Load Speed

1.6 sec in total

First Response

30 ms

Resources Loaded

563 ms

Page Rendered

1 sec

wews.com screenshot

About Website

Visit wews.com now to see the best up-to-date WEWS content and also check out these interesting facts you probably never knew about wews.com

News 5 Cleveland brings you Cleveland news, weather, traffic and sports from the Cleveland metro area and across Ohio on WEWS and News5Cleveland.com

Visit wews.com

Key Findings

We analyzed Wews.com page load time and found that the first response time was 30 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

wews.com performance score

11

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

35/100

10%

LCP (Largest Contentful Paint)

Value45.0 s

0/100

25%

SI (Speed Index)

Value33.9 s

0/100

10%

TBT (Total Blocking Time)

Value41,260 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.234

53/100

15%

TTI (Time to Interactive)

Value88.3 s

0/100

10%

Network Requests Diagram

wews.com

30 ms

www.news5cleveland.com

92 ms

All.min.68be1a1a35349dd37435db0ebd46ef43.gz.css

41 ms

6d6d25e3-5be4-444b-82ae-a8f0bb892234.js

47 ms

otSDKStub.js

54 ms

Our browser made a total of 98 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Wews.com, 78% (76 requests) were made to Ewscripps.brightspotcdn.com and 11% (11 requests) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (245 ms) relates to the external source Ewscripps.brightspotcdn.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 562.2 kB (11%)

Content Size

5.0 MB

After Optimization

4.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Wews.com main page is 5.0 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. Images take 4.3 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 335.1 kB

  • Original 409.9 kB
  • After minification 363.7 kB
  • After compression 74.8 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. This page needs HTML code to be minified as it can gain 46.2 kB, which is 11% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 335.1 kB or 82% of the original size.

Image Optimization

-5%

Potential reduce by 226.2 kB

  • Original 4.3 MB
  • After minification 4.1 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. WEWS images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 870 B

  • Original 228.2 kB
  • After minification 228.2 kB
  • After compression 227.4 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

-0%

Potential reduce by 105 B

  • Original 25.3 kB
  • After minification 25.3 kB
  • After compression 25.2 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. Wews.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 8 (9%)

Requests Now

85

After Optimization

77

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

wews.com

wews.com

30 ms

www.news5cleveland.com

www.news5cleveland.com

92 ms

All.min.68be1a1a35349dd37435db0ebd46ef43.gz.css

All.min.68be1a1a35349dd37435db0ebd46ef43.gz.css

41 ms

6d6d25e3-5be4-444b-82ae-a8f0bb892234.js

6d6d25e3-5be4-444b-82ae-a8f0bb892234.js

47 ms

otSDKStub.js

otSDKStub.js

54 ms

tsu4adm.css

tsu4adm.css

38 ms

BrightspotAdCode.7fe0b8a6b8980a25440dcb5d9f78fba5.gz.js

BrightspotAdCode.7fe0b8a6b8980a25440dcb5d9f78fba5.gz.js

34 ms

All.min.ed716997cb8f3ddfa651e1c0ecb47268.gz.js

All.min.ed716997cb8f3ddfa651e1c0ecb47268.gz.js

43 ms

bsp-analytics.min.3d492319d8b084de04ab3a208c32f0b5.gz.js

bsp-analytics.min.3d492319d8b084de04ab3a208c32f0b5.gz.js

42 ms

gtm.js

gtm.js

216 ms

000000.json

000000.json

196 ms

pushly-sdk.min.js

pushly-sdk.min.js

17 ms

p.css

p.css

29 ms

sdk.js

sdk.js

180 ms

163 ms

logo-scripps.png

logo-scripps.png

241 ms

152 ms

153 ms

152 ms

152 ms

161 ms

235 ms

178 ms

179 ms

179 ms

176 ms

234 ms

184 ms

184 ms

182 ms

181 ms

233 ms

184 ms

230 ms

185 ms

233 ms

232 ms

238 ms

236 ms

237 ms

237 ms

239 ms

240 ms

238 ms

240 ms

241 ms

244 ms

242 ms

245 ms

245 ms

245 ms

d

d

148 ms

d

d

175 ms

d

d

173 ms

d

d

173 ms

d

d

175 ms

113 ms

d

d

35 ms

d

d

39 ms

d

d

38 ms

d

d

38 ms

d

d

38 ms

99 ms

99 ms

99 ms

101 ms

sdk.js

sdk.js

24 ms

77 ms

81 ms

74 ms

72 ms

72 ms

72 ms

73 ms

71 ms

70 ms

71 ms

28 ms

27 ms

27 ms

26 ms

25 ms

26 ms

28 ms

24 ms

24 ms

23 ms

25 ms

23 ms

23 ms

23 ms

23 ms

23 ms

22 ms

21 ms

20 ms

21 ms

480x360.png

480x360.png

21 ms

Accessibility Review

wews.com accessibility score

85

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

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

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

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

wews.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Requests the notification permission on page load

Low

Ensure CSP is effective against XSS attacks

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

wews.com SEO score

83

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 Wews.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 Wews.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

wews.com

Open Graph description is not detected on the main page of WEWS. 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: