Tools & Wizards About Us
wyff.com screenshot

Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 83% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

wyff.com

Greenville SC News and Weather - WYFF News 4

Page Load Speed

1.3 sec in total

First Response

23 ms

Resources Loaded

785 ms

Page Rendered

512 ms

wyff.com screenshot

About Website

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

Get the latest Greenville news and weather. For live, local, late-breaking Greenville, SC, news coverage, WYFF 4 is the place to be.

Visit wyff.com

Key Findings

We analyzed Wyff.com page load time and found that the first response time was 23 ms and then it took 1.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.

Performance Metrics

wyff.com performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

40/100

10%

LCP (Largest Contentful Paint)

Value8.4 s

2/100

25%

SI (Speed Index)

Value13.8 s

1/100

10%

TBT (Total Blocking Time)

Value5,930 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value34.5 s

0/100

10%

Network Requests Diagram

www.wyff4.com

23 ms

script.js

35 ms

gpt.js

216 ms

prebid.js

117 ms

main.js

28 ms

Our browser made a total of 44 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Wyff.com, 16% (7 requests) were made to Kubrick.htvapps.com and 11% (5 requests) were made to Y000.wyff4.com. The less responsive or slowest element that took the longest time to load (346 ms) relates to the external source Js.appboycdn.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 814.7 kB (60%)

Content Size

1.4 MB

After Optimization

550.4 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Wyff.com 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. 65% of websites need less resources to load. Javascripts take 787.4 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 224.5 kB

  • Original 267.8 kB
  • After minification 249.4 kB
  • After compression 43.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 224.5 kB or 84% of the original size.

Image Optimization

-43%

Potential reduce by 133.6 kB

  • Original 309.9 kB
  • After minification 176.3 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. Obviously, WYFF needs image optimization as it can save up to 133.6 kB or 43% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-58%

Potential reduce by 456.6 kB

  • Original 787.4 kB
  • After minification 787.4 kB
  • After compression 330.8 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 456.6 kB or 58% of the original size.

Requests Breakdown

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

Requests Now

35

After Optimization

22

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.wyff4.com

www.wyff4.com

23 ms

script.js

script.js

35 ms

gpt.js

gpt.js

216 ms

prebid.js

prebid.js

117 ms

main.js

main.js

28 ms

Main.374e9bb.js

Main.374e9bb.js

131 ms

761

761

290 ms

c91c24fe6b5fa458228da2.js

c91c24fe6b5fa458228da2.js

288 ms

Bootstrap.js

Bootstrap.js

246 ms

logo.png

logo.png

329 ms

prod_amnews_iframe_section_braze.html

prod_amnews_iframe_section_braze.html

316 ms

unknown_sm.599fcc7.jpg

unknown_sm.599fcc7.jpg

208 ms

default.3b698e2.css

default.3b698e2.css

171 ms

braze.no-amd.min.js

braze.no-amd.min.js

346 ms

pip_prod.json

pip_prod.json

180 ms

IconFont.3f4aa8e.woff

IconFont.3f4aa8e.woff

129 ms

fontawesome.3e829d6.woff

fontawesome.3e829d6.woff

129 ms

pubads_impl.js

pubads_impl.js

309 ms

f5bf64ea-fb37-4311-b879-69fe0923d452_1715884844.file

f5bf64ea-fb37-4311-b879-69fe0923d452_1715884844.file

240 ms

29601

29601

229 ms

d59a2572-3877-4eb4-a191-77786317b98b_1687983912.jpg

d59a2572-3877-4eb4-a191-77786317b98b_1687983912.jpg

313 ms

41926242-armed-robbery-or-shooting-jpg-jpg.jpg

41926242-armed-robbery-or-shooting-jpg-jpg.jpg

106 ms

storm-clouds-64cd25b96d6d0.jpg

storm-clouds-64cd25b96d6d0.jpg

131 ms

tn-booktrip-6646271380770.png

tn-booktrip-6646271380770.png

210 ms

16x9tonight-6595aad03e510.png

16x9tonight-6595aad03e510.png

220 ms

wyff.png

wyff.png

132 ms

wyff.png

wyff.png

132 ms

ef34265dc6f728a43eb79efdfce739f9

ef34265dc6f728a43eb79efdfce739f9

70 ms

fonts-deferred.0da0b82.css

fonts-deferred.0da0b82.css

82 ms

serverComponent.php

serverComponent.php

88 ms

skeleton.gif

skeleton.gif

236 ms

css

css

240 ms

original.png

original.png

263 ms

f39932dfbe7f3f87127fedea9e466c60

f39932dfbe7f3f87127fedea9e466c60

112 ms

LB-Zone-2

LB-Zone-2

215 ms

bafa37b8992be010898976bd2d4beea2.js

bafa37b8992be010898976bd2d4beea2.js

167 ms

23fbe88ca91500b147639538c6ecd87b.js

23fbe88ca91500b147639538c6ecd87b.js

202 ms

montserrat-regular.c95e266.woff

montserrat-regular.c95e266.woff

76 ms

montserrat-bold.f87c625.woff

montserrat-bold.f87c625.woff

76 ms

sourcesanspro-regular.1e8e27e.woff

sourcesanspro-regular.1e8e27e.woff

76 ms

sourcesanspro-bold.7049ba7.woff

sourcesanspro-bold.7049ba7.woff

164 ms

nt_cloudy_sm.a736566.jpg

nt_cloudy_sm.a736566.jpg

123 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aXw.woff

20 ms

6xK3dSBYKcSV-LCoeQqfX1RYOo3qOK7j.woff

6xK3dSBYKcSV-LCoeQqfX1RYOo3qOK7j.woff

23 ms

Accessibility Review

wyff.com accessibility score

94

Accessibility Issues

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.

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

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

wyff.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

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

wyff.com 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

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

wyff.com

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