Report Summary

  • 25

    Performance

    Renders faster than
    44% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 49% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

wdse.org

PBS North • Broadcast and Digital Public Media

Page Load Speed

5.8 sec in total

First Response

1.3 sec

Resources Loaded

3.8 sec

Page Rendered

689 ms

About Website

Click here to check amazing Wdse content for United States. Otherwise, check out these important facts you probably never knew about wdse.org

PBS North is a trusted nonprofit community partner providing broadcast and digital public media since 1964.

Visit wdse.org

Key Findings

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

Performance Metrics

wdse.org performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

26/100

10%

LCP (Largest Contentful Paint)

Value4.6 s

35/100

25%

SI (Speed Index)

Value9.2 s

13/100

10%

TBT (Total Blocking Time)

Value4,560 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.146

77/100

15%

TTI (Time to Interactive)

Value18.0 s

3/100

10%

Network Requests Diagram

wdse.org

1310 ms

css

24 ms

css_84c8140301293bdc7030650f6c904caa.css

204 ms

js_bf3a6094f9d23d17fd560395f838dcfa.js

214 ms

gc.js

11 ms

Our browser made a total of 50 requests to load all elements on the main page. We found that 60% of them (30 requests) were addressed to the original Wdse.org, 18% (9 requests) were made to Pbs-mordor-prod-cdn.s3.amazonaws.com and 8% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Tvss.services.pbs.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 968.2 kB (25%)

Content Size

3.8 MB

After Optimization

2.8 MB

In fact, the total size of Wdse.org main page is 3.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. 45% of websites need less resources to load. Images take 2.8 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 97.5 kB

  • Original 113.3 kB
  • After minification 106.2 kB
  • After compression 15.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. 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 97.5 kB or 86% of the original size.

Image Optimization

-7%

Potential reduce by 201.4 kB

  • Original 2.8 MB
  • After minification 2.6 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. Wdse images are well optimized though.

JavaScript Optimization

-75%

Potential reduce by 440.1 kB

  • Original 587.0 kB
  • After minification 525.7 kB
  • After compression 146.9 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 440.1 kB or 75% of the original size.

CSS Optimization

-85%

Potential reduce by 229.3 kB

  • Original 268.4 kB
  • After minification 240.9 kB
  • After compression 39.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. Wdse.org needs all CSS files to be minified and compressed as it can save up to 229.3 kB or 85% of the original size.

Requests Breakdown

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

Requests Now

45

After Optimization

26

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

Accessibility Review

wdse.org accessibility score

80

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

Links do not have a discernible name

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

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

Page has valid source maps

SEO Factors

wdse.org SEO score

86

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

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

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