Tools & Wizards About Us
wtae.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

wtae.com

Pittsburgh PA News, Weather and Sports - WTAE-TV Pittsburgh Action News 4

Page Load Speed

1.3 sec in total

First Response

23 ms

Resources Loaded

756 ms

Page Rendered

569 ms

wtae.com screenshot

About Website

Welcome to wtae.com homepage info - get ready to check WTAE best content for United States right away, or after learning these important things about wtae.com

Stay in the know with the latest Pittsburgh news, weather and sports. Catch all of the day’s top stories and more from the team at WTAE Pittsburgh Action News 4.

Visit wtae.com

Key Findings

We analyzed Wtae.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 30% of websites can load faster.

Performance Metrics

wtae.com performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

41/100

10%

LCP (Largest Contentful Paint)

Value9.0 s

1/100

25%

SI (Speed Index)

Value15.2 s

1/100

10%

TBT (Total Blocking Time)

Value4,360 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.041

99/100

15%

TTI (Time to Interactive)

Value34.3 s

0/100

10%

Network Requests Diagram

www.wtae.com

23 ms

script.js

41 ms

gpt.js

233 ms

prebid.js

39 ms

main.js

112 ms

Our browser made a total of 43 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Wtae.com, 30% (13 requests) were made to Assets.htvapps.com and 21% (9 requests) were made to Kubrick.htvapps.com. The less responsive or slowest element that took the longest time to load (342 ms) relates to the external source Tm.hdmtools.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 674.0 kB (49%)

Content Size

1.4 MB

After Optimization

695.3 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Wtae.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 713.5 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 232.1 kB

  • Original 276.7 kB
  • After minification 258.5 kB
  • After compression 44.6 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 232.1 kB or 84% of the original size.

Image Optimization

-16%

Potential reduce by 59.6 kB

  • Original 379.1 kB
  • After minification 319.5 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, WTAE needs image optimization as it can save up to 59.6 kB or 16% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-54%

Potential reduce by 382.3 kB

  • Original 713.5 kB
  • After minification 713.5 kB
  • After compression 331.2 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 382.3 kB or 54% of the original size.

Requests Breakdown

Number of requests can be reduced by 15 (42%)

Requests Now

36

After Optimization

21

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.wtae.com

www.wtae.com

23 ms

script.js

script.js

41 ms

gpt.js

gpt.js

233 ms

prebid.js

prebid.js

39 ms

main.js

main.js

112 ms

Main.374e9bb.js

Main.374e9bb.js

114 ms

cs

cs

232 ms

bb03d3f92f1a919fb0b6ba767a8d1baad2f6

bb03d3f92f1a919fb0b6ba767a8d1baad2f6

218 ms

Bootstrap.js

Bootstrap.js

342 ms

logo.png

logo.png

316 ms

default.3b698e2.css

default.3b698e2.css

161 ms

unknown_sm.599fcc7.jpg

unknown_sm.599fcc7.jpg

172 ms

braze.no-amd.min.js

braze.no-amd.min.js

295 ms

pip_prod.json

pip_prod.json

50 ms

IconFont.3f4aa8e.woff

IconFont.3f4aa8e.woff

47 ms

fontawesome.3e829d6.woff

fontawesome.3e829d6.woff

48 ms

pubads_impl.js

pubads_impl.js

148 ms

f8795643-d156-444f-a008-208a189c338e_1477672126.jpg

f8795643-d156-444f-a008-208a189c338e_1477672126.jpg

289 ms

15219

15219

213 ms

848

848

193 ms

122b1b5f-4f0d-4bc0-a803-c6c0d52cad61_1664483234.file

122b1b5f-4f0d-4bc0-a803-c6c0d52cad61_1664483234.file

271 ms

4a0a8774-983a-4c94-a3b0-d2630c50cec6_1653489233.file

4a0a8774-983a-4c94-a3b0-d2630c50cec6_1653489233.file

272 ms

fonts-deferred.0da0b82.css

fonts-deferred.0da0b82.css

91 ms

harrison-city-6647cea477e0f.jpg

harrison-city-6647cea477e0f.jpg

91 ms

screenshot-145-664806877fe78.png

screenshot-145-664806877fe78.png

297 ms

tornado-highland-park-664800686a472.jpg

tornado-highland-park-664800686a472.jpg

201 ms

author_avatar.png

author_avatar.png

200 ms

917f7f26-8cbf-4f14-ac94-60561d82083a.jpg

917f7f26-8cbf-4f14-ac94-60561d82083a.jpg

201 ms

harrison-city-6647cea477e0f.jpg

harrison-city-6647cea477e0f.jpg

227 ms

wtae.png

wtae.png

227 ms

wtae.png

wtae.png

269 ms

skeleton.gif

skeleton.gif

293 ms

serverComponent.php

serverComponent.php

178 ms

montserrat-regular.c95e266.woff

montserrat-regular.c95e266.woff

80 ms

montserrat-bold.f87c625.woff

montserrat-bold.f87c625.woff

79 ms

sourcesanspro-regular.1e8e27e.woff

sourcesanspro-regular.1e8e27e.woff

80 ms

sourcesanspro-bold.7049ba7.woff

sourcesanspro-bold.7049ba7.woff

123 ms

ef34265dc6f728a43eb79efdfce739f9

ef34265dc6f728a43eb79efdfce739f9

74 ms

bafa37b8992be010898976bd2d4beea2.js

bafa37b8992be010898976bd2d4beea2.js

15 ms

23fbe88ca91500b147639538c6ecd87b.js

23fbe88ca91500b147639538c6ecd87b.js

28 ms

f39932dfbe7f3f87127fedea9e466c60

f39932dfbe7f3f87127fedea9e466c60

7 ms

LB-Zone-2

LB-Zone-2

19 ms

cs

cs

3 ms

Accessibility Review

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

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

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

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wtae.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Wtae.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

wtae.com

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