Spin.app Test Results

Spin.app Mobile Performance: 38/100
Quick overview:
Max Potential First Input Delay
690 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.
Time to Interactive
11.1 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.
First Meaningful Paint
4.6 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric.

Spin.app Mobile SEO: 80/100
Quick overview:
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Links do not have descriptive text
3 links found
Descriptive link text helps search engines understand your content. Learn how to make links more accessible.
Document does not have a meta description
Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.
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 how to make pages mobile-friendly.
Tap targets are not sized appropriately
61% appropriately sized tap targets
Interactive elements like buttons and links should be large enough (48x48px), or have enough space around them, to be easy enough to tap without overlapping onto other elements. Learn more about tap targets.

Spin.app Mobile Best Practices: 59/100
Quick overview:
General
Uses deprecated APIs
1 warning found
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
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
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.
Spin.app Mobile PWA: 38/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. 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 about splash screens. 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 about theming the address bar. Failures: No manifest was fetched, No `<meta name="theme-color">` tag found.
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 about manifest installability requirements.
Spin.app Mobile Accessibility: 91/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-hidden="true"]` elements contain focusable descendents
Focusable descendents within an `aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. [Learn how `aria-hidden` affects focusable elements.
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 sites
Similar tests
www.spin.com
www.spin.net
www.spin.org
www.spin.info
www.spin.biz
www.spin.us
www.spin.mobi
www.pin.app
www.spin.app
www.wpin.app
www.swpin.app
www.wspin.app
www.epin.app
www.sepin.app
www.espin.app
www.dpin.app
www.sdpin.app
www.dspin.app
www.zpin.app
www.szpin.app
www.zspin.app
www.xpin.app
www.sxpin.app
www.xspin.app
www.apin.app
www.sapin.app
www.aspin.app
www.sin.app
www.soin.app
www.spoin.app
www.sopin.app
www.slin.app
www.splin.app
www.slpin.app
www.spn.app
www.spun.app
www.spiun.app
www.spuin.app
www.spjn.app
www.spijn.app
www.spjin.app
www.spkn.app
www.spikn.app
www.spkin.app
www.spon.app
www.spion.app
www.spi.app
www.spib.app
www.spinb.app
www.spibn.app
www.spih.app
www.spinh.app
www.spihn.app
www.spij.app
www.spinj.app
www.spim.app
www.spinm.app
www.spimn.app
Last Tested: