Thp.ca Site Title

Trillium Health Partners

Thp.ca Meta Description

Trillium Health Partners - One of Ontario's leaders in delivering exceptional patient care at the Credit Valley Hospital, the Mississauga Hospital and the Queensway Health Centre

Thp.ca Test Results

Thp.ca Mobile Performance: 42/100
Quick overview:
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Serve images in next-gen formats
Potential savings of 483 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.
Minimize main-thread work
3.3 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
Largest Contentful Paint element
13,180 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element
Reduce JavaScript execution time
1.5 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.
Avoid multiple page redirects
Potential savings of 1,110 ms
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Enable text compression
Potential savings of 118 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more about text compression.
Reduce unused CSS
Potential savings of 51 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.
Reduce the impact of third-party code
Third-party code blocked the main thread for 610 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.
Eliminate render-blocking resources
Potential savings of 2,380 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.
Reduce unused JavaScript
Potential savings of 480 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.
Defer offscreen images
Potential savings of 217 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.
Efficiently encode images
Potential savings of 161 KiB
Optimized images load faster and consume less cellular data. Learn how to efficiently encode images.
Serve static assets with an efficient cache policy
9 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
Image elements do not have explicit `width` and `height`
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions
Avoid serving legacy JavaScript to modern browsers
Potential savings of 27 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
Time to Interactive
14.3 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.
First Meaningful Paint
5.5 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric.
Max Potential First Input Delay
250 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.

Thp.ca Mobile SEO: 100/100
Quick overview:

Thp.ca Mobile Best Practices: 62/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
Uses deprecated APIs
3 warnings found
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
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.
Thp.ca Mobile Accessibility: 82/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.
`<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.
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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Heading elements are not in a sequentially-descending order
Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.
Elements with visible text labels do not have matching accessible names.
Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.
Contrast
These are opportunities to improve the legibility of your content.
Background and foreground colors do not have a sufficient contrast ratio.
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
Similar sites
Similar tests
www.thp.com
www.thp.net
www.thp.org
www.thp.info
www.thp.biz
www.thp.us
www.thp.mobi
www.hp.ca
www.thp.ca
www.rhp.ca
www.trhp.ca
www.rthp.ca
www.fhp.ca
www.tfhp.ca
www.fthp.ca
www.ghp.ca
www.tghp.ca
www.gthp.ca
www.yhp.ca
www.tyhp.ca
www.ythp.ca
www.tp.ca
www.tbp.ca
www.thbp.ca
www.tbhp.ca
www.tgp.ca
www.thgp.ca
www.typ.ca
www.thyp.ca
www.tup.ca
www.thup.ca
www.tuhp.ca
www.tjp.ca
www.thjp.ca
www.tjhp.ca
www.tnp.ca
www.thnp.ca
www.tnhp.ca
www.th.ca
www.tho.ca
www.thpo.ca
www.thop.ca
www.thl.ca
www.thpl.ca
www.thlp.ca
Last Tested: