Tools & Wizards About Us
wfae.org screenshot

Report Summary

  • 26

    Performance

    Renders faster than
    45% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

wfae.org

WFAE - Charlotte's NPR News Source | WFAE 90.7 - Charlotte's NPR News Source

Page Load Speed

2.6 sec in total

First Response

34 ms

Resources Loaded

1.3 sec

Page Rendered

1.3 sec

wfae.org screenshot

About Website

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

WFAE 90.7 FM is a major source of breaking news about local issues, politics, government, education, health care, arts, sports, crime, justice, immigration, environment, business, music, podcasts and ...

Visit wfae.org

Key Findings

We analyzed Wfae.org page load time and found that the first response time was 34 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

wfae.org performance score

26

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

45/100

10%

LCP (Largest Contentful Paint)

Value10.1 s

0/100

25%

SI (Speed Index)

Value5.9 s

48/100

10%

TBT (Total Blocking Time)

Value2,130 ms

6/100

30%

CLS (Cumulative Layout Shift)

Value0.079

94/100

15%

TTI (Time to Interactive)

Value17.0 s

4/100

10%

Network Requests Diagram

wfae.org

34 ms

www.wfae.org

11 ms

www.wfae.org

23 ms

All.min.ab6eee59525552b9100e33650d638008.gz.css

28 ms

All.min.4b4833d6fd1d7b8e09869a5338764779.gz.js

145 ms

Our browser made a total of 110 requests to load all elements on the main page. We found that 3% of them (3 requests) were addressed to the original Wfae.org, 72% (79 requests) were made to Npr.brightspotcdn.com and 6% (7 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1 sec) relates to the external source Npr.brightspotcdn.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 394.5 kB (21%)

Content Size

1.9 MB

After Optimization

1.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Wfae.org main page is 1.9 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. 80% 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.1 MB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 359.6 kB

  • Original 413.4 kB
  • After minification 338.6 kB
  • After compression 53.8 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 74.8 kB, which is 18% 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 359.6 kB or 87% of the original size.

Image Optimization

-3%

Potential reduce by 33.7 kB

  • Original 1.1 MB
  • After minification 1.1 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. WFAE images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 73 B

  • Original 350.8 kB
  • After minification 350.8 kB
  • After compression 350.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

-2%

Potential reduce by 1.1 kB

  • Original 66.1 kB
  • After minification 66.1 kB
  • After compression 65.0 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. Wfae.org has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 21 (21%)

Requests Now

102

After Optimization

81

  • AJAX
  • Images
  • JavaScript
  • CSS

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

wfae.org

wfae.org

34 ms

www.wfae.org

www.wfae.org

11 ms

www.wfae.org

www.wfae.org

23 ms

All.min.ab6eee59525552b9100e33650d638008.gz.css

All.min.ab6eee59525552b9100e33650d638008.gz.css

28 ms

All.min.4b4833d6fd1d7b8e09869a5338764779.gz.js

All.min.4b4833d6fd1d7b8e09869a5338764779.gz.js

145 ms

gpt.js

gpt.js

115 ms

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

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

100 ms

gtm.js

gtm.js

341 ms

sdk.js

sdk.js

91 ms

css

css

124 ms

26 ms

406 ms

56 ms

62 ms

61 ms

61 ms

60 ms

65 ms

310 ms

311 ms

64 ms

62 ms

65 ms

67 ms

68 ms

87 ms

89 ms

88 ms

90 ms

90 ms

89 ms

92 ms

92 ms

345 ms

93 ms

196 ms

194 ms

195 ms

197 ms

250 ms

249 ms

251 ms

306 ms

307 ms

1015 ms

pubads_impl.js

pubads_impl.js

41 ms

260 ms

259 ms

255 ms

286 ms

285 ms

287 ms

289 ms

sdk.js

sdk.js

5 ms

285 ms

284 ms

286 ms

284 ms

335 ms

260 ms

316 ms

315 ms

314 ms

317 ms

315 ms

314 ms

313 ms

313 ms

318 ms

214 ms

213 ms

213 ms

211 ms

161 ms

158 ms

164 ms

160 ms

font

font

151 ms

03523cf578d69fa92322.7fd94fa817347c6bd7becf26441c6613.ttf

03523cf578d69fa92322.7fd94fa817347c6bd7becf26441c6613.ttf

157 ms

13a29228654d5c5ec9c4.7b0eb73b656115d05b57f4fa7ecf42d4.ttf

13a29228654d5c5ec9c4.7b0eb73b656115d05b57f4fa7ecf42d4.ttf

106 ms

0cea39826bd36bbfe330.149b470671f9f421e78f806a06dd415d.ttf

0cea39826bd36bbfe330.149b470671f9f421e78f806a06dd415d.ttf

105 ms

4f39c5796e60c9d8e732.cd710cfd3cd36443d1c66b0d79d445c5.ttf

4f39c5796e60c9d8e732.cd710cfd3cd36443d1c66b0d79d445c5.ttf

107 ms

111 ms

167 ms

105 ms

105 ms

72 ms

73 ms

74 ms

73 ms

73 ms

js

js

106 ms

js

js

181 ms

analytics.js

analytics.js

176 ms

gtm.js

gtm.js

163 ms

chartbeat.js

chartbeat.js

161 ms

ping

ping

35 ms

collect

collect

33 ms

collect

collect

38 ms

collect

collect

27 ms

collect

collect

45 ms

collect

collect

25 ms

collect

collect

50 ms

api.min.js

api.min.js

22 ms

js

js

35 ms

ga-audiences

ga-audiences

87 ms

collect

collect

53 ms

ping

ping

23 ms

collect

collect

8 ms

collect

collect

7 ms

Accessibility Review

wfae.org accessibility score

100

Accessibility Issues

Best Practices

wfae.org best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

wfae.org SEO score

99

Search Engine Optimization Advices

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 Wfae.org 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 Wfae.org 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

wfae.org

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