Tools & Wizards About Us
wlex.net screenshot

Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

wlex.net

LEX 18, WLEX, Lexington, Kentucky Breaking News, Weather, Sports and Traffic | LEX18 | WLEX-TV | Lex18.com

Page Load Speed

1.5 sec in total

First Response

29 ms

Resources Loaded

638 ms

Page Rendered

808 ms

wlex.net screenshot

About Website

Welcome to wlex.net homepage info - get ready to check WLEX best content right away, or after learning these important things about wlex.net

WLEX Lex 18 News brings you breaking and developing city news, weather, traffic and sports coverage from the Lexington metro area and across Kentucky on WLEX-TV and Lex18.com.

Visit wlex.net

Key Findings

We analyzed Wlex.net page load time and found that the first response time was 29 ms and then it took 1.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

wlex.net performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

24/100

10%

LCP (Largest Contentful Paint)

Value21.6 s

0/100

25%

SI (Speed Index)

Value31.0 s

0/100

10%

TBT (Total Blocking Time)

Value9,150 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.095

91/100

15%

TTI (Time to Interactive)

Value64.4 s

0/100

10%

Network Requests Diagram

wlex.net

29 ms

www.lex18.com

94 ms

All.min.1fe73e58a0f5c3a32003eb81116a46af.gz.css

46 ms

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

43 ms

otSDKStub.js

55 ms

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

Page Optimization Overview & Recommendations

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

Content Size

5.4 MB

After Optimization

4.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Wlex.net main page is 5.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. 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.8 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 276.2 kB

  • Original 344.9 kB
  • After minification 310.2 kB
  • After compression 68.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 276.2 kB or 80% of the original size.

Image Optimization

-7%

Potential reduce by 329.6 kB

  • Original 4.8 MB
  • After minification 4.4 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. WLEX images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 58 B

  • Original 228.7 kB
  • After minification 228.7 kB
  • After compression 228.7 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 106 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. Wlex.net has all CSS files already compressed.

Requests Breakdown

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

Requests Now

67

After Optimization

58

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

wlex.net

wlex.net

29 ms

www.lex18.com

www.lex18.com

94 ms

All.min.1fe73e58a0f5c3a32003eb81116a46af.gz.css

All.min.1fe73e58a0f5c3a32003eb81116a46af.gz.css

46 ms

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

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

43 ms

otSDKStub.js

otSDKStub.js

55 ms

tsu4adm.css

tsu4adm.css

59 ms

BrightspotAdCode.3d960ee963edb9e76cfc538b6c7a1895.gz.js

BrightspotAdCode.3d960ee963edb9e76cfc538b6c7a1895.gz.js

57 ms

All.min.ed716997cb8f3ddfa651e1c0ecb47268.gz.js

All.min.ed716997cb8f3ddfa651e1c0ecb47268.gz.js

59 ms

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

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

57 ms

gtm.js

gtm.js

203 ms

000000.json

000000.json

23 ms

pushly-sdk.min.js

pushly-sdk.min.js

24 ms

p.css

p.css

26 ms

sdk.js

sdk.js

170 ms

157 ms

logo-scripps.png

logo-scripps.png

238 ms

189 ms

171 ms

190 ms

171 ms

239 ms

235 ms

185 ms

188 ms

233 ms

233 ms

231 ms

231 ms

235 ms

239 ms

236 ms

238 ms

239 ms

240 ms

241 ms

242 ms

239 ms

240 ms

242 ms

244 ms

245 ms

242 ms

246 ms

243 ms

245 ms

245 ms

247 ms

247 ms

246 ms

248 ms

249 ms

d

d

160 ms

d

d

183 ms

d

d

183 ms

d

d

183 ms

d

d

183 ms

d

d

45 ms

d

d

131 ms

d

d

89 ms

d

d

48 ms

d

d

90 ms

108 ms

sdk.js

sdk.js

29 ms

82 ms

69 ms

66 ms

65 ms

65 ms

39 ms

38 ms

36 ms

38 ms

36 ms

110122-positively-480-x-360.jpg

110122-positively-480-x-360.jpg

36 ms

weather

weather

46 ms

breaking-news-alerts

breaking-news-alerts

53 ms

alerts

alerts

52 ms

school-closings-delays

school-closings-delays

60 ms

45 ms

clear.png

clear.png

19 ms

Accessibility Review

wlex.net accessibility score

98

Accessibility Issues

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

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

wlex.net SEO score

90

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

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

wlex.net

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