Fleetx.io Test Results

Fleetx.io Mobile Performance: 78/100
Quick overview:
Document request latency
Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.
Render blocking requests
Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.
Forced reflow
Many APIs, typically reading layout geometry, force the rendering engine to pause script execution in order to calculate the style and layout. Learn more about forced reflow and its mitigations.
Font display
Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.
Use efficient cache lifetimes
Est savings of 279 KiB
A long cache lifetime can speed up repeat visits to your page. Learn more.
Legacy JavaScript
Est savings of 43 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support legacy browsers. Learn why most sites can deploy ES6+ code without transpiling
Improve image delivery
Est savings of 277 KiB
Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size
Time to Interactive
11.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.
Max Potential First Input Delay
220 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
More information about the performance of your application. These numbers don't directly affect the Performance score.
Largest Contentful Paint element
3,890 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element
Avoid multiple page redirects
Est savings of 1,110 ms
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Defer offscreen images
Est savings of 31 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.
Reduce unused JavaScript
Est savings of 185 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.
Properly size images
Est savings of 231 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`.
Avoid serving legacy JavaScript to modern browsers
Est savings of 12 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support legacy browsers. Learn why most sites can deploy ES6+ code without transpiling
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.

Fleetx.io Mobile SEO: 92/100
Quick overview:
Crawling and Indexing
To appear in search results, crawlers need access to your app.
robots.txt is not valid
2 errors found
If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more about robots.txt.

Fleetx.io Mobile Best Practices: 76/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.
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
User Experience
Displays images with incorrect aspect ratio
Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.
Fleetx.io Mobile Accessibility: 90/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.
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.
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Lists do not contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.
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.
Similar tests
www.fleetx.com
www.fleetx.net
www.fleetx.org
www.fleetx.info
www.fleetx.biz
www.fleetx.us
www.fleetx.mobi
www.leetx.io
www.fleetx.io
www.cleetx.io
www.fcleetx.io
www.cfleetx.io
www.dleetx.io
www.fdleetx.io
www.dfleetx.io
www.rleetx.io
www.frleetx.io
www.rfleetx.io
www.tleetx.io
www.ftleetx.io
www.tfleetx.io
www.gleetx.io
www.fgleetx.io
www.gfleetx.io
www.vleetx.io
www.fvleetx.io
www.vfleetx.io
www.feetx.io
www.fpeetx.io
www.flpeetx.io
www.fpleetx.io
www.foeetx.io
www.floeetx.io
www.foleetx.io
www.fkeetx.io
www.flkeetx.io
www.fkleetx.io
www.fletx.io
www.flwetx.io
www.flewetx.io
www.flweetx.io
www.flsetx.io
www.flesetx.io
www.flseetx.io
www.fldetx.io
www.fledetx.io
www.fldeetx.io
www.flretx.io
www.fleretx.io
www.flreetx.io
www.flewtx.io
www.fleewtx.io
www.flestx.io
www.fleestx.io
www.fledtx.io
www.fleedtx.io
www.flertx.io
www.fleertx.io
www.fleex.io
www.fleerx.io
www.fleetrx.io
www.fleefx.io
www.fleetfx.io
www.fleeftx.io
www.fleegx.io
www.fleetgx.io
www.fleegtx.io
www.fleeyx.io
www.fleetyx.io
www.fleeytx.io
www.fleet.io
www.fleetz.io
www.fleetxz.io
www.fleetzx.io
www.fleets.io
www.fleetxs.io
www.fleetsx.io
www.fleetd.io
www.fleetxd.io
www.fleetdx.io
www.fleetc.io
www.fleetxc.io
www.fleetcx.io
Last Tested: