Hp.ca Site Title
Laptop Computers, Desktops, Printers, Ink & Toner | HP® Canada
Hp.ca Meta Description
Learn about HP printers, laptops, desktops and more at the Official HP® Website
Hp.ca Test Results
Hp.ca Mobile Performance: 14/100
Quick overview:
Max Potential First Input Delay
590 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.
Time to Interactive
13.4 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
4.9 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric.
Script Treemap Data
Used for treemap app
Network Round Trip Times
0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance. Learn more about the Round Trip Time.
Network Requests
Lists the network requests that were made during page load.
Final Screenshot
The last screenshot captured of the pageload.
1089728792438
Server Backend Latencies
0 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance. Learn more about server response time.
Tasks
Lists the toplevel main thread tasks that executed during page load.
Diagnostics
Collection of useful page vitals.
Metrics
Collects all available metrics.
Hp.ca Mobile SEO: 83/100
Quick overview:
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 how to make pages mobile-friendly.
Tap targets are not sized appropriately
65% appropriately sized tap targets
Interactive elements like buttons and links should be large enough (48x48px), or have enough space around them, to be easy enough to tap without overlapping onto other elements. Learn more about tap targets.
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Links are not crawlable
Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Links do not have descriptive text
2 links found
Descriptive link text helps search engines understand your content. Learn how to make links more accessible.
Hp.ca Mobile Best Practices: 83/100
Quick overview:
Trust and Safety
Does not use HTTPS
3 insecure requests 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.
Ensure CSP is effective against XSS attacks
A strong Content Security Policy (CSP) significantly reduces the risk of cross-site scripting (XSS) attacks. Learn how to use a CSP to prevent XSS
General
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.
Registers an `unload` listener
The `unload` event does not fire reliably and listening for it can prevent browser optimizations like the Back-Forward Cache. Use `pagehide` or `visibilitychange` events instead. Learn more about unload event listeners
Hp.ca Mobile PWA: 33/100
Quick overview:
PWA Optimized
Does not register a service worker that controls page and `start_url`
The service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. Learn more about Service Workers.
Does not set a theme color for the address bar.
The browser address bar can be themed to match your site. Learn more about theming the address bar. Failures: No manifest was fetched,
No `<meta name="theme-color">` tag found.
Manifest doesn't have a maskable icon
A maskable icon ensures that the image fills the entire shape without being letterboxed when installing the app on a device. Learn about maskable manifest icons. No manifest was fetched
Is not configured for a custom splash screen
A themed splash screen ensures a high-quality experience when users launch your app from their homescreens. Learn more about splash screens. Failures: No manifest was fetched.
Installable
Web app manifest or service worker do not meet the installability requirements
1 reason
Service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. With proper service worker and manifest implementations, browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement. Learn more about manifest installability requirements.
Hp.ca Mobile Accessibility: 88/100
Quick overview:
Navigation
These are opportunities to improve keyboard navigation in your application.
Some elements have a `[tabindex]` value greater than 0
A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the `tabindex` attribute.
`[id]` attributes on active, focusable elements are not unique
All focusable elements must have a unique `id` to ensure that they're visible to assistive technologies. Learn how to fix duplicate `id`s.
Best practices
These items highlight common accessibility best practices.
`[user-scalable="no"]` is used in the `<meta name="viewport">` element or the `[maximum-scale]` attribute is less than 5.
Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.
Similar sites
Similar tests
www.hp.com
www.hp.net
www.hp.org
www.hp.info
www.hp.biz
www.hp.us
www.hp.mobi
www.p.ca
www.hp.ca
www.bp.ca
www.hbp.ca
www.bhp.ca
www.gp.ca
www.hgp.ca
www.ghp.ca
www.yp.ca
www.hyp.ca
www.yhp.ca
www.up.ca
www.hup.ca
www.uhp.ca
www.jp.ca
www.hjp.ca
www.jhp.ca
www.np.ca
www.hnp.ca
www.nhp.ca
www.h.ca
www.ho.ca
www.hpo.ca
www.hop.ca
www.hl.ca
www.hpl.ca
www.hlp.ca
www.hp.net
www.hp.org
www.hp.info
www.hp.biz
www.hp.us
www.hp.mobi
www.p.ca
www.hp.ca
www.bp.ca
www.hbp.ca
www.bhp.ca
www.gp.ca
www.hgp.ca
www.ghp.ca
www.yp.ca
www.hyp.ca
www.yhp.ca
www.up.ca
www.hup.ca
www.uhp.ca
www.jp.ca
www.hjp.ca
www.jhp.ca
www.np.ca
www.hnp.ca
www.nhp.ca
www.h.ca
www.ho.ca
www.hpo.ca
www.hop.ca
www.hl.ca
www.hpl.ca
www.hlp.ca