Airbase.com Test Results

Airbase.com Mobile Performance: 34/100
Quick overview:
Opportunities
These suggestions can help your page load faster. They don't directly affect the Performance score.
Eliminate render-blocking resources. Potential savings of 8,000 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.
Avoid multiple page redirects. Potential savings of 1,110 ms
Redirects introduce additional delays before the page can be loaded. Learn more.
Remove unused CSS. Potential savings of 101 KiB
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity. Learn more.
Remove unused JavaScript. Potential savings of 158 KiB
Remove unused JavaScript to reduce bytes consumed by network activity. Learn more.
Serve images in next-gen formats. Potential savings of 54 KiB
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more.
Minify JavaScript. Potential savings of 46 KiB
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.
Properly size images. Potential savings of 67 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.
Avoid serving legacy JavaScript to modern browsers. Potential savings of 30 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 More
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
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 more
Reduce the impact of third-party code
Third-party code blocked the main thread for 300 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 more.
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.
Does not use passive listeners to improve scrolling performance
Consider marking your touch and wheel event listeners as `passive` to improve your page's scroll performance. Learn more.
Minimize main-thread work
4.8 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more
Serve static assets with an efficient cache policy
12 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.
Reduce JavaScript execution time
1.8 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.
Avoid an excessive DOM size
893 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn more.
Keep request counts low and transfer sizes small
126 requests • 2,369 KiB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.
Largest Contentful Paint element
1 element found
This is the largest contentful element painted within the viewport. Learn More
Avoid chaining critical requests
9 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn more.
Avoid long main-thread tasks
16 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn more
Avoid large layout shifts
1 element found
These DOM elements contribute most to the CLS of the page.

Airbase.com Mobile SEO: 99/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 more.
Tap targets are not sized appropriately
90% appropriately sized tap targets
Interactive elements like buttons and links should be large enough (48x48px), and have enough space around them, to be easy enough to tap without overlapping onto other elements. Learn more.

Airbase.com Mobile Best Practices: 73/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.
Links to cross-origin destinations are unsafe
Add `rel="noopener"` or `rel="noreferrer"` to any external links to improve performance and prevent security vulnerabilities. Learn more.
General
Registers an `unload` listener
The `unload` event does not fire reliably and listening for it can prevent browser optimizations like the Back-Forward Cache. Consider using the `pagehide` or `visibilitychange` events instead. Learn more
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
Airbase.com Mobile Progressive Web App: 50/100
Quick overview:
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.
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 more. 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. Failures: No manifest was fetched.
Does not set a theme color for the address bar.
The browser address bar can be themed to match your site. Learn more. Failures: No manifest was fetched, No `<meta name="theme-color">` tag found.
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.
Airbase.com Mobile Accessibility: 94/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 more.
Navigation
These are opportunities to improve keyboard navigation in your application.
`[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 more.
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 more.
Similar sites
Similar tests
www.airbase.com
www.airbase.net
www.airbase.org
www.airbase.info
www.airbase.biz
www.airbase.us
www.airbase.mobi
www.irbase.com
www.airbase.com
www.qirbase.com
www.aqirbase.com
www.qairbase.com
www.wirbase.com
www.awirbase.com
www.wairbase.com
www.sirbase.com
www.asirbase.com
www.sairbase.com
www.zirbase.com
www.azirbase.com
www.zairbase.com
www.arbase.com
www.aurbase.com
www.aiurbase.com
www.auirbase.com
www.ajrbase.com
www.aijrbase.com
www.ajirbase.com
www.akrbase.com
www.aikrbase.com
www.akirbase.com
www.aorbase.com
www.aiorbase.com
www.aoirbase.com
www.aibase.com
www.aiebase.com
www.airebase.com
www.aierbase.com
www.aidbase.com
www.airdbase.com
www.aidrbase.com
www.aifbase.com
www.airfbase.com
www.aifrbase.com
www.aitbase.com
www.airtbase.com
www.aitrbase.com
www.airase.com
www.airvase.com
www.airbvase.com
www.airvbase.com
www.airgase.com
www.airbgase.com
www.airgbase.com
www.airhase.com
www.airbhase.com
www.airhbase.com
www.airnase.com
www.airbnase.com
www.airnbase.com
www.airbse.com
www.airbqse.com
www.airbaqse.com
www.airbqase.com
www.airbwse.com
www.airbawse.com
www.airbwase.com
www.airbsse.com
www.airbasse.com
www.airbsase.com
www.airbzse.com
www.airbazse.com
www.airbzase.com
www.airbae.com
www.airbawe.com
www.airbaswe.com
www.airbaee.com
www.airbasee.com
www.airbaese.com
www.airbade.com
www.airbasde.com
www.airbadse.com
www.airbaze.com
www.airbasze.com
www.airbaxe.com
www.airbasxe.com
www.airbaxse.com
www.airbaae.com
www.airbasae.com
www.airbaase.com
www.airbas.com
www.airbasw.com
www.airbasew.com
www.airbass.com
www.airbases.com
www.airbasd.com
www.airbased.com
www.airbasr.com
www.airbaser.com
www.airbasre.com
www.airbase.con
Last Tested: