Tools & Wizards About Us
wfts.com screenshot

Report Summary

  • 13

    Performance

    Renders faster than
    25% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

wfts.com

Tampa Bay, Florida News and Weather | Tampa Bay 28

Page Load Speed

1.9 sec in total

First Response

30 ms

Resources Loaded

752 ms

Page Rendered

1.2 sec

wfts.com screenshot

About Website

Click here to check amazing Wfts content. Otherwise, check out these important facts you probably never knew about wfts.com

Get the latest Tampa Bay news, weather forecasts, traffic updates, and more from Tampa Bay 28

Visit wfts.com

Key Findings

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

Performance Metrics

wfts.com performance score

13

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

35/100

10%

LCP (Largest Contentful Paint)

Value39.2 s

0/100

25%

SI (Speed Index)

Value32.5 s

0/100

10%

TBT (Total Blocking Time)

Value2,330 ms

5/100

30%

CLS (Cumulative Layout Shift)

Value0.242

51/100

15%

TTI (Time to Interactive)

Value56.5 s

0/100

10%

Network Requests Diagram

wfts.com

30 ms

www.abcactionnews.com

59 ms

All.min.68be1a1a35349dd37435db0ebd46ef43.gz.css

43 ms

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

49 ms

otSDKStub.js

58 ms

Our browser made a total of 125 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Wfts.com, 60% (75 requests) were made to Ewscripps.brightspotcdn.com and 14% (17 requests) were made to Assets.scrippsdigital.com. The less responsive or slowest element that took the longest time to load (314 ms) relates to the external source Ewscripps.brightspotcdn.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 847.7 kB (9%)

Content Size

9.6 MB

After Optimization

8.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Wfts.com main page is 9.6 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. Only a small number of websites need less resources to load. Images take 8.5 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 321.9 kB

  • Original 398.2 kB
  • After minification 353.9 kB
  • After compression 76.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. This page needs HTML code to be minified as it can gain 44.3 kB, which is 11% 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 321.9 kB or 81% of the original size.

Image Optimization

-6%

Potential reduce by 523.7 kB

  • Original 8.5 MB
  • After minification 7.9 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. Wfts images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 1.9 kB

  • Original 689.7 kB
  • After minification 689.7 kB
  • After compression 687.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 105 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. Wfts.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 25 (23%)

Requests Now

111

After Optimization

86

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

wfts.com

wfts.com

30 ms

www.abcactionnews.com

www.abcactionnews.com

59 ms

All.min.68be1a1a35349dd37435db0ebd46ef43.gz.css

All.min.68be1a1a35349dd37435db0ebd46ef43.gz.css

43 ms

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

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

49 ms

otSDKStub.js

otSDKStub.js

58 ms

tsu4adm.css

tsu4adm.css

55 ms

BrightspotAdCode.7fe0b8a6b8980a25440dcb5d9f78fba5.gz.js

BrightspotAdCode.7fe0b8a6b8980a25440dcb5d9f78fba5.gz.js

47 ms

All.min.ed716997cb8f3ddfa651e1c0ecb47268.gz.js

All.min.ed716997cb8f3ddfa651e1c0ecb47268.gz.js

49 ms

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

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

47 ms

gtm.js

gtm.js

214 ms

000000.json

000000.json

30 ms

pushly-sdk.min.js

pushly-sdk.min.js

23 ms

p.css

p.css

34 ms

sdk.js

sdk.js

180 ms

ua-sdk.min.js

ua-sdk.min.js

293 ms

163 ms

I-TEAM_728x150.jpg

I-TEAM_728x150.jpg

279 ms

logo-scripps.png

logo-scripps.png

270 ms

167 ms

167 ms

291 ms

293 ms

296 ms

292 ms

292 ms

252 ms

264 ms

289 ms

298 ms

297 ms

296 ms

302 ms

302 ms

299 ms

300 ms

299 ms

300 ms

302 ms

303 ms

305 ms

314 ms

304 ms

304 ms

306 ms

308 ms

306 ms

309 ms

312 ms

307 ms

308 ms

310 ms

313 ms

311 ms

d

d

150 ms

d

d

195 ms

d

d

195 ms

d

d

208 ms

d

d

208 ms

d

d

67 ms

d

d

114 ms

d

d

113 ms

d

d

114 ms

d

d

114 ms

172 ms

sdk.js

sdk.js

58 ms

151 ms

128 ms

61 ms

53 ms

31 ms

30 ms

31 ms

29 ms

28 ms

26 ms

26 ms

28 ms

26 ms

26 ms

25 ms

28 ms

25 ms

26 ms

28 ms

24 ms

25 ms

25 ms

26 ms

26 ms

35 ms

25 ms

24 ms

25 ms

23 ms

30 ms

24 ms

21 ms

21 ms

abc-action-news-plus-1280x720.png

abc-action-news-plus-1280x720.png

24 ms

weather

weather

59 ms

breaking-news-alerts

breaking-news-alerts

67 ms

alerts

alerts

60 ms

school-closings-delays

school-closings-delays

61 ms

player.html

player.html

59 ms

partlycloudy.png

partlycloudy.png

47 ms

pwt.js

pwt.js

109 ms

apstag.js

apstag.js

33 ms

ima3.js

ima3.js

51 ms

hls.min.js

hls.min.js

49 ms

conviva-core-sdk.js

conviva-core-sdk.js

21 ms

conviva-html5native-impl.js

conviva-html5native-impl.js

29 ms

ua-parser.min.js

ua-parser.min.js

30 ms

20 ms

code-solid.svg

code-solid.svg

14 ms

stopwatch-solid.svg

stopwatch-solid.svg

11 ms

camcorder-solid.svg

camcorder-solid.svg

16 ms

return-solid.svg

return-solid.svg

12 ms

play-solid.svg

play-solid.svg

16 ms

next-solid.svg

next-solid.svg

17 ms

volume-muted-solid.svg

volume-muted-solid.svg

18 ms

cog-solid.svg

cog-solid.svg

21 ms

cc-solid.svg

cc-solid.svg

18 ms

pip-solid.svg

pip-solid.svg

18 ms

cast-solid.svg

cast-solid.svg

21 ms

expand-wide-solid.svg

expand-wide-solid.svg

19 ms

Accessibility Review

wfts.com accessibility score

85

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

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

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

wfts.com SEO score

83

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

Content Best Practices

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

Impact

Issue

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

wfts.com

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