Hub.safe.com Site Title
FME Hub
Hub.safe.com Test Results
Hub.safe.com Mobile Performance: 26/100
Quick overview:
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Reduce unused CSS
Potential savings of 110 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.
Avoid serving legacy JavaScript to modern browsers
Potential savings of 20 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
Minimize main-thread work
10.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
Efficiently encode images
Potential savings of 67 KiB
Optimized images load faster and consume less cellular data. Learn how to efficiently encode images.
Serve images in next-gen formats
Potential savings of 299 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.
Reduce JavaScript execution time
6.9 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 unused JavaScript
Potential savings of 906 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.
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.
Eliminate render-blocking resources
Potential savings of 150 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.
Largest Contentful Paint element
13,920 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element
Properly size images
Potential savings of 153 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.
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`.
Serve static assets with an efficient cache policy
7 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
Reduce the impact of third-party code
Third-party code blocked the main thread for 470 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.
Defer offscreen images
Potential savings of 9 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.
Max Potential First Input Delay
2,340 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
10.2 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
13.8 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.
Hub.safe.com Mobile SEO: 100/100
Quick overview:
Hub.safe.com Mobile Best Practices: 83/100
Quick overview:
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.
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.
Hub.safe.com Mobile Accessibility: 73/100
Quick overview:
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.
`[aria-*]` attributes do not match their roles
Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn how to match ARIA attributes to their roles.
ARIA `progressbar` elements do not have accessible names.
When a `progressbar` element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to label `progressbar` elements.
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.
Select elements do not have associated label elements.
Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.
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.
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.
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.
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.
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.
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 tests
www.hub.com
www.hub.net
www.hub.org
www.hub.info
www.hub.biz
www.hub.us
www.hub.mobi
www.ub.safe.com
www.hub.safe.com
www.bub.safe.com
www.hbub.safe.com
www.bhub.safe.com
www.gub.safe.com
www.hgub.safe.com
www.ghub.safe.com
www.yub.safe.com
www.hyub.safe.com
www.yhub.safe.com
www.uub.safe.com
www.huub.safe.com
www.uhub.safe.com
www.jub.safe.com
www.hjub.safe.com
www.jhub.safe.com
www.nub.safe.com
www.hnub.safe.com
www.nhub.safe.com
www.hb.safe.com
www.hyb.safe.com
www.huyb.safe.com
www.hhb.safe.com
www.huhb.safe.com
www.hhub.safe.com
www.hjb.safe.com
www.hujb.safe.com
www.hib.safe.com
www.huib.safe.com
www.hiub.safe.com
www.hu.safe.com
www.huv.safe.com
www.hubv.safe.com
www.huvb.safe.com
www.hug.safe.com
www.hubg.safe.com
www.hugb.safe.com
www.huh.safe.com
www.hubh.safe.com
www.hun.safe.com
www.hubn.safe.com
www.hunb.safe.com
www.hub.net
www.hub.org
www.hub.info
www.hub.biz
www.hub.us
www.hub.mobi
www.ub.safe.com
www.hub.safe.com
www.bub.safe.com
www.hbub.safe.com
www.bhub.safe.com
www.gub.safe.com
www.hgub.safe.com
www.ghub.safe.com
www.yub.safe.com
www.hyub.safe.com
www.yhub.safe.com
www.uub.safe.com
www.huub.safe.com
www.uhub.safe.com
www.jub.safe.com
www.hjub.safe.com
www.jhub.safe.com
www.nub.safe.com
www.hnub.safe.com
www.nhub.safe.com
www.hb.safe.com
www.hyb.safe.com
www.huyb.safe.com
www.hhb.safe.com
www.huhb.safe.com
www.hhub.safe.com
www.hjb.safe.com
www.hujb.safe.com
www.hib.safe.com
www.huib.safe.com
www.hiub.safe.com
www.hu.safe.com
www.huv.safe.com
www.hubv.safe.com
www.huvb.safe.com
www.hug.safe.com
www.hubg.safe.com
www.hugb.safe.com
www.huh.safe.com
www.hubh.safe.com
www.hun.safe.com
www.hubn.safe.com
www.hunb.safe.com