Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 39% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

wltx.com

Columbia's Leading Local News: Weather, Traffic, Sports and more | Columbia, South Carolina | WLTX.com | wltx.com

Page Load Speed

1.6 sec in total

First Response

130 ms

Resources Loaded

715 ms

Page Rendered

792 ms

About Website

Click here to check amazing WLTX content for United States. Otherwise, check out these important facts you probably never knew about wltx.com

Visit wltx.com

Key Findings

We analyzed Wltx.com page load time and found that the first response time was 130 ms and then it took 1.5 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

wltx.com performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

50/100

10%

LCP (Largest Contentful Paint)

Value34.2 s

0/100

25%

SI (Speed Index)

Value24.4 s

0/100

10%

TBT (Total Blocking Time)

Value20,560 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.008

100/100

15%

TTI (Time to Interactive)

Value58.6 s

0/100

10%

Network Requests Diagram

wltx.com

130 ms

www.wltx.com

91 ms

otSDKStub.js

62 ms

otCCPAiab.js

77 ms

api.js

51 ms

Our browser made a total of 72 requests to load all elements on the main page. We found that 31% of them (22 requests) were addressed to the original Wltx.com, 57% (41 requests) were made to Media.wltx.com and 6% (4 requests) were made to Cdn.cookielaw.org. The less responsive or slowest element that took the longest time to load (341 ms) belongs to the original domain Wltx.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 467.4 kB (17%)

Content Size

2.8 MB

After Optimization

2.3 MB

In fact, the total size of Wltx.com main page is 2.8 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 1.9 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 281.6 kB

  • Original 326.1 kB
  • After minification 281.6 kB
  • After compression 44.5 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 44.5 kB, which is 14% 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 281.6 kB or 86% of the original size.

Image Optimization

-6%

Potential reduce by 114.4 kB

  • Original 1.9 MB
  • After minification 1.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. WLTX images are well optimized though.

JavaScript Optimization

-11%

Potential reduce by 51.3 kB

  • Original 478.6 kB
  • After minification 478.6 kB
  • After compression 427.3 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 51.3 kB or 11% of the original size.

CSS Optimization

-40%

Potential reduce by 20.0 kB

  • Original 49.6 kB
  • After minification 49.6 kB
  • After compression 29.5 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. Wltx.com needs all CSS files to be minified and compressed as it can save up to 20.0 kB or 40% of the original size.

Requests Breakdown

Number of requests can be reduced by 29 (49%)

Requests Now

59

After Optimization

30

The browser has sent 59 CSS, Javascripts, AJAX and image requests in order to completely render the main page of WLTX. 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.

Accessibility Review

wltx.com accessibility score

73

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

High

button, link, and menuitem elements do not have accessible names.

High

[aria-hidden="true"] elements contain focusable descendents

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

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

High

Some elements have a [tabindex] value greater than 0

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

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

wltx.com best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

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

wltx.com SEO score

69

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

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

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