Pbs.org PBS: Public Broadcasting Service
Watch full episodes of your favorite PBS shows, explore music and the arts, find in-depth news analysis, and more. Home to Antiques Roadshow, Frontlin...
pbs.org Desktop Performance
70/100
These metrics represent real-world Chrome users experience viewing pbs.org web page. Reports are focused on loading performance and other critical factors that most affect user experience. Follow our guide to track, optimize, and improve the quality of your web pages.
User Loading Experience
First Input Delay
Largest Contentful Paint
Cumulative Layout Shift
First Contentful Paint
Metrics
Total Blocking Time40/100 410 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more.
Speed Index48/100 2.4 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
Largest Contentful Paint82/100 1.5 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn More
Time to Interactive91/100 2.4 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
First Contentful Paint91/100 0.9 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
Cumulative Layout Shift100/100 0.024
Cumulative Layout Shift measures the movement of visible elements within the viewport. Learn more.
Should Fix (13)
Opportunities
These suggestions can help your page load faster. They don't directly affect the Performance score.
Avoid multiple page redirects
Potential savings of 380 ms
380 ms
Remove unused JavaScript
Potential savings of 417 KiB
380 ms
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Does not use passive listeners to improve scrolling performance
Serve static assets with an efficient cache policy
17 resources found
Avoid an excessive DOM size
1,625 elements
Minimize main-thread work
2.2 s
Reduce JavaScript execution time
1.3 s
Largest Contentful Paint element
1 element found
Keep request counts low and transfer sizes small
81 requests • 1,455 KiB
Avoid chaining critical requests
13 chains found
Avoid long main-thread tasks
4 long tasks found
User Timing marks and measures
1 user timing
Avoid large layout shifts
5 elements found
Passed Audits (17)
Use video formats for animated content
Minimize third-party usage
Third-party code blocked the main thread for 10 ms
Properly size images
Potential savings of 52 KiB
Minify JavaScript
Potential savings of 9 KiB
Preconnect to required origins
Avoids enormous network payloads
Total size was 1,455 KiB
Enable text compression
Efficiently encode images
All text remains visible during webfont loads
Eliminate render-blocking resources
Potential savings of 40 ms
Remove unused CSS
Potential savings of 17 KiB
Preload key requests
Minify CSS
Serve images in next-gen formats
Potential savings of 23 KiB
Initial server response time was short
Root document took 140 ms
Defer offscreen images
Potential savings of 46 KiB
Avoids `document.write()`
pbs.org Desktop SEO
92/100
These checks ensure that your page is optimized for search engine results ranking. There are additional factors Lighthouse does not check that may affect your search ranking. Learn more. Run these additional validators on your site to check additional SEO best practices.
Should Fix (1)
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Links are not crawlable
Passed Audits (11)
Document has a valid `rel=canonical`
Links have descriptive text
Document has a valid `hreflang`
Document has a `<title>` element
Image elements have `[alt]` attributes
Page isn’t blocked from indexing
Document avoids plugins
Document has a meta description
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
robots.txt is valid
Page has successful HTTP status code
pbs.org Desktop Best Practices
77/100
These checks highlight opportunities to improve the overall code health of pbs.org page. Current recommendations will help to make your page fast and secure, to create a good user experience and to avoid deprecated technologies.
Should Fix (3)
General
Uses deprecated APIs
1 warning found
Browser errors were logged to the console
Trust and Safety
Does not use HTTPS
2 insecure requests found
Passed Audits (11)
Detected JavaScript libraries
Allows users to paste into password fields
Serves images with appropriate resolution
Avoids front-end JavaScript libraries with known security vulnerabilities
Links to cross-origin destinations are safe
Avoids requesting the notification permission on page load
Page has the HTML doctype
Avoids requesting the geolocation permission on page load
Avoids Application Cache
Displays images with correct aspect ratio
Properly defines charset
pbs.org Desktop Progressive Web App
37/100
These checks validate the aspects of a Progressive Web App. Learn more. These checks are required by the baseline PWA Checklist but are not automatically checked by Lighthouse. They do not affect your score but it's important that you verify them manually.
Should Fix (6)
Fast and reliable
Page load is not fast enough on mobile networks
Interactive on simulated mobile network at 13.1 s
Current page does not respond with a 200 when offline
`start_url` does not respond with a 200 when offline
PWA Optimized
Manifest doesn't have a maskable icon
Installable
Does not use HTTPS
2 insecure requests found
Does not register a service worker that controls page and `start_url`
Passed Audits (7)
Configured for a custom splash screen
Provides a valid `apple-touch-icon`
Sets a theme color for the address bar.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
Redirects HTTP traffic to HTTPS
Web app manifest meets the installability requirements
Contains some content when JavaScript is not available
pbs.org Desktop Accessibility
92/100
These checks highlight opportunities to improve the accessibility of your web app. Only a subset of accessibility issues can be automatically detected so manual testing is also encouraged. These items address areas which an automated testing tool cannot cover. Learn more in our guide on conducting an accessibility review.
Should Fix (2)
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.
ARIA IDs are not unique
Contrast
These are opportunities to improve the legibility of your content.
Background and foreground colors do not have a sufficient contrast ratio.
Passed Audits (23)
No element has a `[tabindex]` value greater than 0
`[aria-hidden="true"]` is not present on the document `<body>`
`[role]` values are valid
`[aria-*]` attributes are valid and not misspelled
`[role]`s have all required `[aria-*]` attributes
Buttons have an accessible name
`[aria-hidden="true"]` elements do not contain focusable descendents
`[aria-*]` attributes have valid values
`[id]` attributes on active, focusable elements are unique
Form elements have associated labels
Document has a `<title>` element
`[role]`s are contained by their required parent element
Image elements have `[alt]` attributes
Links have a discernible name
Heading elements appear in a sequentially-descending order
`<html>` element has a `[lang]` attribute
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
`<html>` element has a valid value for its `[lang]` attribute
The page contains a heading, skip link, or landmark region
`[aria-*]` attributes match their roles
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
Desktop Speed
81/100
These checks analyze the performance of pbs.org on desktop devices and return PageSpeed score and information on how to improve the load time. What makes a good Progressive Web App?
Should Fix (3)
Eliminate render-blocking JavaScript and CSS in above-the-fold content
Optimize images
Leverage browser caching
Passed Audits (7)
Avoid landing page redirects
Enable compression
Reduce server response time
Minify CSS
Minify HTML
Minify JavaScript
Prioritize visible content
www.pbs.com
www.pbs.net
www.pbs.org
www.pbs.info
www.pbs.biz
www.pbs.us
www.pbs.mobi
www.bs.org
www.pbs.org
www.obs.org
www.pobs.org
www.opbs.org
www.lbs.org
www.plbs.org
www.lpbs.org
www.ps.org
www.pvs.org
www.pbvs.org
www.pvbs.org
www.pgs.org
www.pbgs.org
www.pgbs.org
www.phs.org
www.pbhs.org
www.phbs.org
www.pns.org
www.pbns.org
www.pnbs.org
www.pb.org
www.pbw.org
www.pbsw.org
www.pbws.org
www.pbe.org
www.pbse.org
www.pbes.org
www.pbd.org
www.pbsd.org
www.pbds.org
www.pbz.org
www.pbsz.org
www.pbzs.org
www.pbx.org
www.pbsx.org
www.pbxs.org
www.pba.org
www.pbsa.org
www.pbas.org
www.pbs.net
www.pbs.org
www.pbs.info
www.pbs.biz
www.pbs.us
www.pbs.mobi
www.bs.org
www.pbs.org
www.obs.org
www.pobs.org
www.opbs.org
www.lbs.org
www.plbs.org
www.lpbs.org
www.ps.org
www.pvs.org
www.pbvs.org
www.pvbs.org
www.pgs.org
www.pbgs.org
www.pgbs.org
www.phs.org
www.pbhs.org
www.phbs.org
www.pns.org
www.pbns.org
www.pnbs.org
www.pb.org
www.pbw.org
www.pbsw.org
www.pbws.org
www.pbe.org
www.pbse.org
www.pbes.org
www.pbd.org
www.pbsd.org
www.pbds.org
www.pbz.org
www.pbsz.org
www.pbzs.org
www.pbx.org
www.pbsx.org
www.pbxs.org
www.pba.org
www.pbsa.org
www.pbas.org