Nwpb.org Site Title
Northwest Public Broadcasting
Nwpb.org Meta Description
NWPB is dedicated to enriching our community by sharing and creating distinctive programs which engage, enlighten and entertain.
Nwpb.org Test Results
Nwpb.org Mobile Performance: 36/100
Quick overview:
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Eliminate render-blocking resources
Potential savings of 1,840 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn how to eliminate render-blocking resources.
Avoid an excessive DOM size
1,153 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn how to avoid an excessive DOM size.
Properly size images
Potential savings of 110 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.
Reduce the impact of third-party code
Third-party code blocked the main thread for 510 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn how to minimize third-party impact.
Largest Contentful Paint element
16,230 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element
Serve images in next-gen formats
Potential savings of 2,952 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more about modern image formats.
Avoid multiple page redirects
Potential savings of 630 ms
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Reduce unused CSS
Potential savings of 208 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.
Minimize main-thread work
5.7 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work
Reduce unused JavaScript
Potential savings of 534 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.
Efficiently encode images
Potential savings of 150 KiB
Optimized images load faster and consume less cellular data. Learn how to efficiently encode images.
Reduce JavaScript execution time
2.8 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.
Reduce initial server response time
Root document took 1,360 ms
Keep the server response time for the main document short because all other requests depend on it. Learn more about the Time to First Byte metric.
Defer offscreen images
Potential savings of 744 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn how to defer offscreen images.
Avoid enormous network payloads
Total size was 5,432 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
Ensure text remains visible during webfont load
Leverage the `font-display` CSS feature to ensure text is user-visible while webfonts are loading. Learn more about `font-display`.
Avoid serving legacy JavaScript to modern browsers
Potential savings of 6 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers. Learn how to use modern JavaScript
Minify CSS
Potential savings of 32 KiB
Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.
Minify JavaScript
Potential savings of 17 KiB
Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.
Serve static assets with an efficient cache policy
71 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
Time to Interactive
22.6 s
Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.
Max Potential First Input Delay
300 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.
First Meaningful Paint
3.6 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric.
Nwpb.org Mobile SEO: 100/100
Quick overview:
Nwpb.org Mobile Best Practices: 72/100
Quick overview:
General
Browser errors were logged to the console
Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit
Missing source maps for large first-party JavaScript
Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.
Issues were logged in the `Issues` panel in Chrome Devtools
Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.
Trust and Safety
Does not use HTTPS
1 insecure request found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more about HTTPS.
User Experience
Serves images with low resolution
Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn how to provide responsive images.
Nwpb.org Mobile Accessibility: 79/100
Quick overview:
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.
Buttons do not have an accessible name
When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.
Links do not have a discernible name
Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.
`<frame>` or `<iframe>` elements do not have a title
Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.
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.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` are missing some or all of those required children.
Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.
Best practices
These items highlight common accessibility best practices.
Touch targets do not have sufficient size or spacing.
Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.
Similar sites
Similar tests
www.nwpb.com
www.nwpb.net
www.nwpb.org
www.nwpb.info
www.nwpb.biz
www.nwpb.us
www.nwpb.mobi
www.wpb.org
www.nwpb.org
www.bwpb.org
www.nbwpb.org
www.bnwpb.org
www.hwpb.org
www.nhwpb.org
www.hnwpb.org
www.jwpb.org
www.njwpb.org
www.jnwpb.org
www.mwpb.org
www.nmwpb.org
www.mnwpb.org
www.npb.org
www.nqpb.org
www.nwqpb.org
www.nqwpb.org
www.napb.org
www.nwapb.org
www.nawpb.org
www.nspb.org
www.nwspb.org
www.nswpb.org
www.nepb.org
www.nwepb.org
www.newpb.org
www.nwb.org
www.nwob.org
www.nwpob.org
www.nwopb.org
www.nwlb.org
www.nwplb.org
www.nwlpb.org
www.nwp.org
www.nwpv.org
www.nwpbv.org
www.nwpvb.org
www.nwpg.org
www.nwpbg.org
www.nwpgb.org
www.nwph.org
www.nwpbh.org
www.nwphb.org
www.nwpn.org
www.nwpbn.org
www.nwpnb.org
www.nwpb.net
www.nwpb.org
www.nwpb.info
www.nwpb.biz
www.nwpb.us
www.nwpb.mobi
www.wpb.org
www.nwpb.org
www.bwpb.org
www.nbwpb.org
www.bnwpb.org
www.hwpb.org
www.nhwpb.org
www.hnwpb.org
www.jwpb.org
www.njwpb.org
www.jnwpb.org
www.mwpb.org
www.nmwpb.org
www.mnwpb.org
www.npb.org
www.nqpb.org
www.nwqpb.org
www.nqwpb.org
www.napb.org
www.nwapb.org
www.nawpb.org
www.nspb.org
www.nwspb.org
www.nswpb.org
www.nepb.org
www.nwepb.org
www.newpb.org
www.nwb.org
www.nwob.org
www.nwpob.org
www.nwopb.org
www.nwlb.org
www.nwplb.org
www.nwlpb.org
www.nwp.org
www.nwpv.org
www.nwpbv.org
www.nwpvb.org
www.nwpg.org
www.nwpbg.org
www.nwpgb.org
www.nwph.org
www.nwpbh.org
www.nwphb.org
www.nwpn.org
www.nwpbn.org
www.nwpnb.org