Tools & Wizards About Us
lee.net screenshot

Report Summary

  • 32

    Performance

    Renders faster than
    52% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 0

    Best Practices

  • 84

    SEO

    Google-friendlier than
    52% of websites

lee.net

Lee Enterprises | Leading Provider of Local News

Page Load Speed

2.5 sec in total

First Response

68 ms

Resources Loaded

2 sec

Page Rendered

414 ms

lee.net screenshot

About Website

Visit lee.net now to see the best up-to-date Lee content for United States and also check out these interesting facts you probably never knew about lee.net

Leading source of local news, information, and advertising in 72 US markets.

Visit lee.net

Key Findings

We analyzed Lee.net page load time and found that the first response time was 68 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

lee.net performance score

32

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

17/100

10%

LCP (Largest Contentful Paint)

Value4.5 s

37/100

25%

SI (Speed Index)

Value5.6 s

54/100

10%

TBT (Total Blocking Time)

Value6,450 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.029

100/100

15%

TTI (Time to Interactive)

Value16.9 s

5/100

10%

Network Requests Diagram

lee.net

68 ms

lee.net

129 ms

bootstrap.min.87df60d54091cf1e8f8173c2e568260c.css

131 ms

layout.5bce7eb56c23d79d6ab89ab093c281ea.css

102 ms

lee-dsv2.css

96 ms

Our browser made a total of 83 requests to load all elements on the main page. We found that 8% of them (7 requests) were addressed to the original Lee.net, 36% (30 requests) were made to Bloximages.chicago2.vip.townnews.com and 8% (7 requests) were made to Cdn.cookielaw.org. The less responsive or slowest element that took the longest time to load (1 sec) relates to the external source Polyfill.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 222.6 kB (16%)

Content Size

1.4 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Lee.net main page is 1.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. 75% 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 687.0 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 154.3 kB

  • Original 195.1 kB
  • After minification 183.3 kB
  • After compression 40.7 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 154.3 kB or 79% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 687.0 kB
  • After minification 687.0 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. Lee images are well optimized though.

JavaScript Optimization

-13%

Potential reduce by 56.1 kB

  • Original 428.1 kB
  • After minification 428.0 kB
  • After compression 372.0 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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 56.1 kB or 13% of the original size.

CSS Optimization

-20%

Potential reduce by 12.2 kB

  • Original 60.1 kB
  • After minification 60.1 kB
  • After compression 47.9 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. Lee.net needs all CSS files to be minified and compressed as it can save up to 12.2 kB or 20% of the original size.

Requests Breakdown

Number of requests can be reduced by 44 (59%)

Requests Now

74

After Optimization

30

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

lee.net

lee.net

68 ms

lee.net

lee.net

129 ms

bootstrap.min.87df60d54091cf1e8f8173c2e568260c.css

bootstrap.min.87df60d54091cf1e8f8173c2e568260c.css

131 ms

layout.5bce7eb56c23d79d6ab89ab093c281ea.css

layout.5bce7eb56c23d79d6ab89ab093c281ea.css

102 ms

lee-dsv2.css

lee-dsv2.css

96 ms

otSDKStub.js

otSDKStub.js

67 ms

osano.js

osano.js

32 ms

access.d7adebba498598b0ec2c.js

access.d7adebba498598b0ec2c.js

85 ms

jquery.min.d6d18fcf88750a16d256e72626e676a6.js

jquery.min.d6d18fcf88750a16d256e72626e676a6.js

93 ms

user.js

user.js

96 ms

bootstrap.min.d457560d3dfbf1d56a225eb99d7b0702.js

bootstrap.min.d457560d3dfbf1d56a225eb99d7b0702.js

94 ms

common.08a61544f369cc43bf02e71b2d10d49f.js

common.08a61544f369cc43bf02e71b2d10d49f.js

112 ms

tnt.ee95c0b6f1daceb31bf5ef84353968c6.js

tnt.ee95c0b6f1daceb31bf5ef84353968c6.js

113 ms

application.3c64d611e594b45dd35b935162e79d85.js

application.3c64d611e594b45dd35b935162e79d85.js

116 ms

polyfill.min.js

polyfill.min.js

1025 ms

tnt.navigation.accessibility.7a9170240d21440159b9bd59db72933b.js

tnt.navigation.accessibility.7a9170240d21440159b9bd59db72933b.js

113 ms

tnt.ads.adverts.66a3812a7b5c12fde8cd998fd691ad7d.js

tnt.ads.adverts.66a3812a7b5c12fde8cd998fd691ad7d.js

116 ms

tracking.js

tracking.js

114 ms

otCCPAiab.js

otCCPAiab.js

65 ms

fontawesome.568f3d1ab17b33ce05854081baadadac.js

fontawesome.568f3d1ab17b33ce05854081baadadac.js

126 ms

aos.css

aos.css

91 ms

aos.js

aos.js

113 ms

tracker.js

tracker.js

116 ms

op.js

op.js

53 ms

gtm.js

gtm.js

42 ms

59bcee1d-30cb-4800-b2a5-a38e78086c31.json

59bcee1d-30cb-4800-b2a5-a38e78086c31.json

99 ms

analytics.js

analytics.js

18 ms

gtm.js

gtm.js

22 ms

gtm.js

gtm.js

40 ms

location

location

72 ms

publisher:getClientId

publisher:getClientId

101 ms

destination

destination

33 ms

otBannerSdk.js

otBannerSdk.js

127 ms

collect

collect

101 ms

collect

collect

129 ms

collect

collect

109 ms

collect

collect

27 ms

en.json

en.json

45 ms

ga-audiences

ga-audiences

78 ms

otFloatingFlat.json

otFloatingFlat.json

22 ms

otPcCenter.json

otPcCenter.json

23 ms

df00eabe-ccd3-11e8-843c-c3fc8b26d9cd.png

df00eabe-ccd3-11e8-843c-c3fc8b26d9cd.png

43 ms

stl.png

stl.png

43 ms

buffalo.png

buffalo.png

45 ms

mad.png

mad.png

47 ms

omaha.png

omaha.png

45 ms

nwi.png

nwi.png

46 ms

ljs.png

ljs.png

129 ms

tucson.png

tucson.png

126 ms

richmond.png

richmond.png

130 ms

amp.png

amp.png

127 ms

sunny.png

sunny.png

128 ms

health.png

health.png

129 ms

bas.png

bas.png

132 ms

blox-devices.png

blox-devices.png

132 ms

f51e9ac8-ccef-11e8-a998-db577153ab30.png

f51e9ac8-ccef-11e8-a998-db577153ab30.png

130 ms

dnsfeed

dnsfeed

120 ms

tracker.gif

tracker.gif

37 ms

gtm.js

gtm.js

110 ms

5e59ba3f1173a.hires.jpg

5e59ba3f1173a.hires.jpg

93 ms

lee-map-2020v2.png

lee-map-2020v2.png

94 ms

5e59bcf8891ec.hires.jpg

5e59bcf8891ec.hires.jpg

95 ms

serif-ds.woff

serif-ds.woff

68 ms

analytics.min.js

analytics.min.js

174 ms

5b5dc540-ca6c-013a-51e3-0cc47a8ffaac

5b5dc540-ca6c-013a-51e3-0cc47a8ffaac

92 ms

js

js

95 ms

linkid.js

linkid.js

27 ms

e3999b3c-9a05-11ea-88f3-811b60505f1b.js

e3999b3c-9a05-11ea-88f3-811b60505f1b.js

56 ms

iframe

iframe

156 ms

settings

settings

10 ms

collect

collect

6 ms

collect

collect

29 ms

870.bundle.6e2976b75e60ab2b2bf8.js

870.bundle.6e2976b75e60ab2b2bf8.js

116 ms

tsub-middleware.bundle.77315eced46c5ae4c052.js

tsub-middleware.bundle.77315eced46c5ae4c052.js

116 ms

ga-audiences

ga-audiences

118 ms

ml.gz.js

ml.gz.js

10 ms

i

i

22 ms

rubicon

rubicon

47 ms

appnexus

appnexus

4 ms

pixel

pixel

53 ms

pixel

pixel

23 ms

google

google

5 ms

41c950c1-bb0e-11ea-939b-4dfa69282fbd.js

41c950c1-bb0e-11ea-939b-4dfa69282fbd.js

28 ms

Accessibility Review

lee.net accessibility score

81

Accessibility Issues

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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.

SEO Factors

lee.net SEO score

84

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Links do not have descriptive text

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 Lee.net 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 Lee.net 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

lee.net

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