2 sec in total
28 ms
1 sec
985 ms
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.netWe analyzed Wlex.net page load time and found that the first response time was 28 ms and then it took 2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
wlex.net performance score
name
value
score
weighting
Value4.7 s
13/100
10%
Value39.4 s
0/100
25%
Value41.8 s
0/100
10%
Value14,920 ms
0/100
30%
Value0.095
91/100
15%
Value68.4 s
0/100
10%
28 ms
46 ms
81 ms
80 ms
81 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 Wlex.net, 53% (52 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 (770 ms) relates to the external source Warp.media.net.
Page size can be reduced by 1.6 MB (22%)
7.2 MB
5.6 MB
In fact, the total size of Wlex.net main page is 7.2 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. 85% 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.
Potential reduce by 304.3 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 304.3 kB or 80% of the original size.
Potential reduce by 178.2 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. WLEX images are well optimized though.
Potential reduce by 1.0 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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 1.0 MB or 56% of the original size.
Potential reduce by 115.1 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 needs all CSS files to be minified and compressed as it can save up to 115.1 kB or 69% of the original size.
Number of requests can be reduced by 20 (24%)
84
64
The browser has sent 84 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 15 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
wlex.net
28 ms
www.lex18.com
46 ms
fontawesome.css
81 ms
brands.css
80 ms
solid.css
81 ms
all.js
150 ms
All.min.e31ea3be13f7f6d9149815d9f177049d.gz.css
36 ms
cookie-consent.css
42 ms
6d6d25e3-5be4-444b-82ae-a8f0bb892234.js
62 ms
otSDKStub.js
74 ms
tsu4adm.css
143 ms
All.min.c468a29d42cfcd96f3c3e90eb095eecd.gz.js
54 ms
bsp-analytics.min.3d492319d8b084de04ab3a208c32f0b5.gz.js
38 ms
gtm.js
203 ms
000000.json
23 ms
apstag.js
24 ms
bidexchange.js
485 ms
clientag.js
770 ms
p.css
36 ms
sdk.js
226 ms
154 ms
logo-scripps.png
207 ms
141 ms
400 ms
139 ms
143 ms
412 ms
401 ms
184 ms
183 ms
183 ms
335 ms
336 ms
333 ms
355 ms
356 ms
354 ms
397 ms
398 ms
397 ms
401 ms
406 ms
400 ms
401 ms
401 ms
407 ms
406 ms
406 ms
408 ms
411 ms
413 ms
410 ms
412 ms
410 ms
411 ms
414 ms
413 ms
d
73 ms
d
116 ms
d
116 ms
d
211 ms
d
211 ms
fa-solid-900.ttf
284 ms
d
209 ms
d
210 ms
d
265 ms
d
264 ms
d
283 ms
350 ms
analytics.js
248 ms
beacon.js
244 ms
weather
222 ms
breaking-news-alerts
221 ms
alerts
219 ms
school-closings-delays
216 ms
js
60 ms
277 ms
277 ms
sdk.js
157 ms
259 ms
238 ms
238 ms
236 ms
92 ms
88 ms
71 ms
69 ms
68 ms
110122-positively-480-x-360.jpg
69 ms
linkid.js
39 ms
cloudy.png
50 ms
34 ms
collect
25 ms
collect
40 ms
collect
20 ms
collect
47 ms
collect
26 ms
collect
48 ms
wlex.net accessibility score
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
wlex.net best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
wlex.net SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
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.
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: