Qub.ca Test Results
Qub.ca Mobile Performance: 2/100
Quick overview:
First Meaningful Paint
11.7 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric.
Time to Interactive
29.2 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
1,190 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.
Diagnostics
Collection of useful page vitals.
Final Screenshot
The last screenshot captured of the pageload.
118915776512
Resources Summary
Aggregates all network requests and groups them by type
Script Treemap Data
Used for treemap app
Network Requests
Lists the network requests that were made during page load.
Metrics
Collects all available metrics.
Tasks
Lists the toplevel main thread tasks that executed during page load.
Server Backend Latencies
350 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.
Network Round Trip Times
80 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.
Qub.ca Mobile SEO: 100/100
Quick overview:
Qub.ca Mobile Best Practices: 78/100
Quick overview:
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.
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.
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.
Detected JavaScript libraries
All front-end JavaScript libraries detected on the page. Learn more about this JavaScript library detection diagnostic audit.
Qub.ca Mobile PWA: 75/100
Quick overview:
PWA Optimized
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.
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: Manifest does not have a PNG icon of at least 512px.
Qub.ca Mobile Accessibility: 92/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.
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.
Touch targets have sufficient size and 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.qub.com
www.qub.net
www.qub.org
www.qub.info
www.qub.biz
www.qub.us
www.qub.mobi
www.ub.ca
www.qub.ca
www.aub.ca
www.qaub.ca
www.aqub.ca
www.wub.ca
www.qwub.ca
www.wqub.ca
www.qb.ca
www.qyb.ca
www.quyb.ca
www.qyub.ca
www.qhb.ca
www.quhb.ca
www.qhub.ca
www.qjb.ca
www.qujb.ca
www.qjub.ca
www.qib.ca
www.quib.ca
www.qiub.ca
www.qu.ca
www.quv.ca
www.qubv.ca
www.quvb.ca
www.qug.ca
www.qubg.ca
www.qugb.ca
www.quh.ca
www.qubh.ca
www.qun.ca
www.qubn.ca
www.qunb.ca
www.qub.net
www.qub.org
www.qub.info
www.qub.biz
www.qub.us
www.qub.mobi
www.ub.ca
www.qub.ca
www.aub.ca
www.qaub.ca
www.aqub.ca
www.wub.ca
www.qwub.ca
www.wqub.ca
www.qb.ca
www.qyb.ca
www.quyb.ca
www.qyub.ca
www.qhb.ca
www.quhb.ca
www.qhub.ca
www.qjb.ca
www.qujb.ca
www.qjub.ca
www.qib.ca
www.quib.ca
www.qiub.ca
www.qu.ca
www.quv.ca
www.qubv.ca
www.quvb.ca
www.qug.ca
www.qubg.ca
www.qugb.ca
www.quh.ca
www.qubh.ca
www.qun.ca
www.qubn.ca
www.qunb.ca