Report Summary

  • 13

    Performance

    Renders faster than
    25% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 67% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

tpt.org

TPT - Twin Cities PBS

Page Load Speed

2.9 sec in total

First Response

96 ms

Resources Loaded

1.9 sec

Page Rendered

950 ms

tpt.org screenshot

About Website

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

Watch TPT shows online. See full episodes, previews, television schedules, information, events and find out how you can support TPT – Twin Cities PBS.

Visit tpt.org

Key Findings

We analyzed Tpt.org page load time and found that the first response time was 96 ms and then it took 2.9 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

tpt.org performance score

13

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.2 s

3/100

10%

LCP (Largest Contentful Paint)

Value10.3 s

0/100

25%

SI (Speed Index)

Value7.3 s

28/100

10%

TBT (Total Blocking Time)

Value1,730 ms

10/100

30%

CLS (Cumulative Layout Shift)

Value0.282

43/100

15%

TTI (Time to Interactive)

Value21.6 s

1/100

10%

Network Requests Diagram

www.tpt.org

96 ms

wp-emoji-release.min.js

9 ms

font-awesome.min.css

9 ms

vendor.css

13 ms

style.css

20 ms

Our browser made a total of 93 requests to load all elements on the main page. We found that 55% of them (51 requests) were addressed to the original Tpt.org, 9% (8 requests) were made to and 6% (6 requests) were made to Sumome-140a.kxcdn.com. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Rpwt.rphelios.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.4 MB (34%)

Content Size

4.1 MB

After Optimization

2.7 MB

In fact, the total size of Tpt.org main page is 4.1 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 2.2 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 59.7 kB

  • Original 71.3 kB
  • After minification 54.6 kB
  • After compression 11.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. This page needs HTML code to be minified as it can gain 16.7 kB, which is 23% 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 59.7 kB or 84% of the original size.

Image Optimization

-1%

Potential reduce by 15.6 kB

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

JavaScript Optimization

-68%

Potential reduce by 724.9 kB

  • Original 1.1 MB
  • After minification 1.1 MB
  • After compression 337.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 724.9 kB or 68% of the original size.

CSS Optimization

-73%

Potential reduce by 601.3 kB

  • Original 821.4 kB
  • After minification 817.9 kB
  • After compression 220.1 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. Tpt.org needs all CSS files to be minified and compressed as it can save up to 601.3 kB or 73% of the original size.

Requests Breakdown

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

Requests Now

81

After Optimization

47

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

Accessibility Review

tpt.org accessibility score

87

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

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.

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Some elements have a [tabindex] value greater than 0

Best Practices

tpt.org best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

tpt.org SEO score

92

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

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tpt.org can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Tpt.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 data is detected on the main page of TPT. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: