Nearbyme.io Site Title

Airfind Portal

Nearbyme.io Test Results

Nearbyme.io Mobile Performance: 62/100
Quick overview:
Opportunities
These suggestions can help your page load faster. They don't directly affect the Performance score.
Remove unused JavaScript. Potential savings of 128 KiB
Remove unused JavaScript to reduce bytes consumed by network activity. Learn more.
Avoid serving legacy JavaScript to modern browsers. Potential savings of 26 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
Properly size images. Potential savings of 11 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.
Serve images in next-gen formats. Potential savings of 14 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.
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
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.
Serve static assets with an efficient cache policy
14 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.
Avoid long main-thread tasks
3 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn more
Keep request counts low and transfer sizes small
35 requests • 535 KiB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.
Avoid large layout shifts
5 elements found
These DOM elements contribute most to the CLS of the page.
Avoid chaining critical requests
1 chain 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.
Largest Contentful Paint element
1 element found
This is the largest contentful element painted within the viewport. Learn More
User Timing marks and measures
1 user timing
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more.

Nearbyme.io Mobile SEO: 77/100
Quick overview:
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Page is blocked from indexing
Search engines are unable to include your pages in search results if they don't have permission to crawl them. Learn more.
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Image elements do not have `[alt]` attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more.
Document does not have a meta description
Meta descriptions may be included in search results to concisely summarize page content. Learn more.

Nearbyme.io Mobile Best Practices: 93/100
Quick overview:
Trust and Safety
Does not use HTTPS
12 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.
Nearbyme.io Mobile Progressive Web App: 50/100
Quick overview:
PWA Optimized
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: Manifest does not have a PNG icon of at least 512px.
Does not redirect HTTP traffic to HTTPS
If you've already set up HTTPS, make sure that you redirect all HTTP traffic to HTTPS in order to enable secure web features for all your users. Learn more.
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.
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 `<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 more.
Nearbyme.io Mobile Accessibility: 41/100
Quick overview:
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
`<html>` element does not have a `[lang]` attribute
If a page doesn't specify a lang attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more.
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.
Image elements do not have `[alt]` attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more.
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 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.
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.
The document uses `<meta http-equiv="refresh">`
Users do not expect a page to refresh automatically, and doing so will move focus back to the top of the page. This may create a frustrating or confusing experience. Learn more.
Similar tests
www.nearbyme.com
www.nearbyme.net
www.nearbyme.org
www.nearbyme.info
www.nearbyme.biz
www.nearbyme.us
www.nearbyme.mobi
www.earbyme.io
www.nearbyme.io
www.bearbyme.io
www.nbearbyme.io
www.bnearbyme.io
www.hearbyme.io
www.nhearbyme.io
www.hnearbyme.io
www.jearbyme.io
www.njearbyme.io
www.jnearbyme.io
www.mearbyme.io
www.nmearbyme.io
www.mnearbyme.io
www.narbyme.io
www.nwarbyme.io
www.newarbyme.io
www.nwearbyme.io
www.nsarbyme.io
www.nesarbyme.io
www.nsearbyme.io
www.ndarbyme.io
www.nedarbyme.io
www.ndearbyme.io
www.nrarbyme.io
www.nerarbyme.io
www.nrearbyme.io
www.nerbyme.io
www.neqrbyme.io
www.neaqrbyme.io
www.neqarbyme.io
www.newrbyme.io
www.neawrbyme.io
www.nesrbyme.io
www.neasrbyme.io
www.nezrbyme.io
www.neazrbyme.io
www.nezarbyme.io
www.neabyme.io
www.neaebyme.io
www.nearebyme.io
www.neaerbyme.io
www.neadbyme.io
www.neardbyme.io
www.neadrbyme.io
www.neafbyme.io
www.nearfbyme.io
www.neafrbyme.io
www.neatbyme.io
www.neartbyme.io
www.neatrbyme.io
www.nearyme.io
www.nearvyme.io
www.nearbvyme.io
www.nearvbyme.io
www.neargyme.io
www.nearbgyme.io
www.neargbyme.io
www.nearhyme.io
www.nearbhyme.io
www.nearhbyme.io
www.nearnyme.io
www.nearbnyme.io
www.nearnbyme.io
www.nearbme.io
www.nearbtme.io
www.nearbytme.io
www.nearbtyme.io
www.nearbgme.io
www.nearbygme.io
www.nearbhme.io
www.nearbyhme.io
www.nearbume.io
www.nearbyume.io
www.nearbuyme.io
www.nearbye.io
www.nearbyne.io
www.nearbymne.io
www.nearbynme.io
www.nearbyje.io
www.nearbymje.io
www.nearbyjme.io
www.nearbyke.io
www.nearbymke.io
www.nearbykme.io
www.nearbym.io
www.nearbymw.io
www.nearbymew.io
www.nearbymwe.io
www.nearbyms.io
www.nearbymes.io
www.nearbymse.io
www.nearbymd.io
www.nearbymed.io
www.nearbymde.io
www.nearbymr.io
www.nearbymer.io
www.nearbymre.io
Last Tested:

This website uses cookies to ensure you get the best experience on our website. Learn more. Got it.