Rpc.ca Request Rejected
rpc.ca Mobile Performance
56/100
These metrics represent real-world Chrome users experience viewing rpc.ca on mobile devices. 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.
Metrics
Largest Contentful Paint2/100 8.3 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn More
First Contentful Paint53/100 3.9 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
Time to Interactive63/100 6.1 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Speed Index71/100 4.6 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
Total Blocking Time89/100 300 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more.
Cumulative Layout Shift100/100 0.001
Cumulative Layout Shift measures the movement of visible elements within the viewport. Learn more.
Should Fix (14)
Opportunities
These suggestions can help your page load faster. They don't directly affect the Performance score.
Eliminate render-blocking resources
Potential savings of 1,640 ms
1,639 ms
Serve images in next-gen formats
Potential savings of 168 KiB
1,350 ms
Remove unused JavaScript
Potential savings of 99 KiB
1,050 ms
Minify JavaScript
Potential savings of 57 KiB
300 ms
Enable text compression
Potential savings of 27 KiB
150 ms
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Ensure text remains visible during webfont load
Serve static assets with an efficient cache policy
40 resources found
Minimize main-thread work
2.6 s
JavaScript execution time
1.2 s
Largest Contentful Paint element
1 element found
Avoid large layout shifts
5 elements found
Avoid chaining critical requests
15 chains found
Avoid long main-thread tasks
10 long tasks found
Keep request counts low and transfer sizes small
60 requests • 1,022 KiB
Passed Audits (15)
Defer offscreen images
Use video formats for animated content
Remove unused CSS
Properly size images
Initial server response time was short
Root document took 320 ms
Minimize third-party usage
Third-party code blocked the main thread for 240 ms
Avoids `document.write()`
Preload key requests
Efficiently encode images
Avoids enormous network payloads
Total size was 1,022 KiB
Avoid multiple page redirects
Potential savings of 630 ms
Uses passive listeners to improve scrolling performance
Preconnect to required origins
Avoids an excessive DOM size
541 elements
Minify CSS
rpc.ca Mobile SEO
69/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 (4)
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Image elements do not have `[alt]` attributes
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.
Document doesn't use legible font sizes
Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
Tap targets are not sized appropriately
Passed Audits (9)
Document has a valid `hreflang`
Document avoids plugins
Links have descriptive text
Page isn’t blocked from indexing
Document has a meta description
Page has successful HTTP status code
robots.txt is valid
Links are crawlable
Document has a `<title>` element
rpc.ca Mobile Best Practices
54/100
These checks highlight opportunities to improve the overall code health of rpc.ca mobile 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 (6)
Trust and Safety
Includes front-end JavaScript libraries with known security vulnerabilities
4 vulnerabilities detected
Links to cross-origin destinations are unsafe
Does not use HTTPS
40 insecure requests found
User Experience
Serves images with low resolution
General
Browser errors were logged to the console
Browser Compatibility
Page lacks the HTML doctype, thus triggering quirks-mode
Passed Audits (8)
Avoids requesting the notification permission on page load
Avoids requesting the geolocation permission on page load
Avoids Application Cache
Properly defines charset
Avoids deprecated APIs
Detected JavaScript libraries
Allows users to paste into password fields
Displays images with correct aspect ratio
rpc.ca Mobile Progressive Web App
29/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 (12)
Fast and reliable
Current page does not respond with a 200 when offline
`start_url` does not respond with a 200 when offline
PWA Optimized
Content is not sized correctly for the viewport
Does not redirect HTTP traffic to HTTPS
Is not configured for a custom splash screen
Does not provide a valid `apple-touch-icon`
Manifest doesn't have a maskable icon
Does not set a theme color for the address bar.
Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
Installable
Web app manifest does not meet the installability requirements
Does not use HTTPS
40 insecure requests found
Does not register a service worker that controls page and `start_url`
Passed Audits (2)
Contains some content when JavaScript is not available
Page load is fast enough on mobile networks
rpc.ca Mobile Accessibility
52/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 (6)
Navigation
These are opportunities to improve keyboard navigation in your application.
The page does not contain a heading, skip link, or landmark region
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.
Links do not have a discernible name
Image elements do not have `[alt]` attributes
`<frame>` or `<iframe>` elements do not have a title
Form elements do not have associated labels
Contrast
These are opportunities to improve the legibility of your content.
Background and foreground colors do not have a sufficient contrast ratio.
Passed Audits (9)
`<html>` element has a valid value for its `[lang]` attribute
`[aria-hidden="true"]` is not present on the document `<body>`
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
Presentational `<table>` elements avoid using `<th>`, `<caption>` or the `[summary]` attribute.
`<html>` element has a `[lang]` attribute
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Document has a `<title>` element
Mobile Usability
67/100
These checks validate how easily a visitor can use rpc.ca on a mobile device. Test results include a list of any mobile usability problems. Mobile usability problems are issues that can affect a user that visits the page on a mobile (small screen) device, including small font sizes (which are hard to read on a small screen).
Should Fix (2)
Use legible font sizes
Configure the viewport
Passed Audits (3)
Avoid plugins
Size content to viewport
Size tap targets appropriately
Mobile Speed
100/100
These checks analyze the performance of rpc.ca on mobile devices and return PageSpeed score and information on how to improve the load time. What makes a good Progressive Web App?
Passed Audits (10)
Avoid landing page redirects
Enable compression
Leverage browser caching
Reduce server response time
Minify CSS
Minify HTML
Minify JavaScript
Eliminate render-blocking JavaScript and CSS in above-the-fold content
Optimize images
Prioritize visible content
www.rpc.com
www.rpc.net
www.rpc.org
www.rpc.info
www.rpc.biz
www.rpc.us
www.rpc.mobi
www.pc.ca
www.rpc.ca
www.epc.ca
www.repc.ca
www.erpc.ca
www.dpc.ca
www.rdpc.ca
www.drpc.ca
www.fpc.ca
www.rfpc.ca
www.frpc.ca
www.tpc.ca
www.rtpc.ca
www.trpc.ca
www.rc.ca
www.roc.ca
www.rpoc.ca
www.ropc.ca
www.rlc.ca
www.rplc.ca
www.rlpc.ca
www.rp.ca
www.rpx.ca
www.rpcx.ca
www.rpxc.ca
www.rpd.ca
www.rpcd.ca
www.rpdc.ca
www.rpf.ca
www.rpcf.ca
www.rpfc.ca
www.rpv.ca
www.rpcv.ca
www.rpvc.ca
www.rpc.net
www.rpc.org
www.rpc.info
www.rpc.biz
www.rpc.us
www.rpc.mobi
www.pc.ca
www.rpc.ca
www.epc.ca
www.repc.ca
www.erpc.ca
www.dpc.ca
www.rdpc.ca
www.drpc.ca
www.fpc.ca
www.rfpc.ca
www.frpc.ca
www.tpc.ca
www.rtpc.ca
www.trpc.ca
www.rc.ca
www.roc.ca
www.rpoc.ca
www.ropc.ca
www.rlc.ca
www.rplc.ca
www.rlpc.ca
www.rp.ca
www.rpx.ca
www.rpcx.ca
www.rpxc.ca
www.rpd.ca
www.rpcd.ca
www.rpdc.ca
www.rpf.ca
www.rpcf.ca
www.rpfc.ca
www.rpv.ca
www.rpcv.ca
www.rpvc.ca