osv.dev - OSV

Osv.dev Site Title

OSV

Osv.dev Test Results

Osv.dev Mobile Performance: 65/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 145 KiB

Remove unused JavaScript to reduce bytes consumed by network activity. Learn more.

Properly size images. Potential savings of 163 KiB

Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.

Remove unused CSS. Potential savings of 41 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.

Avoid serving legacy JavaScript to modern browsers. Potential savings of 12 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.

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.

Minimize main-thread work

3.3 s

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. 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.

Keep request counts low and transfer sizes small

10 requests • 10,290 KiB

To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Avoid long main-thread tasks

9 long tasks found

Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn more

Largest Contentful Paint element

1 element found

This is the largest contentful element painted within the viewport. Learn More

Avoid large layout shifts

4 elements found

These DOM elements contribute most to the CLS of the page.

Osv.dev Mobile SEO: 69/100

Quick overview:

Crawling and Indexing

To appear in search results, crawlers need access to your app.

robots.txt is not valid

4 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.

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

1 link found

Descriptive link text helps search engines understand your content. Learn more.

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.

Osv.dev Mobile Best Practices: 86/100

Quick overview:

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

Trust and Safety

Does not use HTTPS

8 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 servedover 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.

Osv.dev Mobile Progressive Web App: 39/100

Quick overview:

PWA Optimized

Does not provide a valid `apple-touch-icon`

For ideal appearance on iOS when users add a progressive web app to the home screen, define an `apple-touch-icon`. It must point to a non-transparent 192px (or 180px) square PNG. 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 manifest was fetched, 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. 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 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.

Fast and reliable

`start_url` does not respond with a 200 when offline

A service worker enables your web app to be reliable in unpredictable network conditions. Learn more. No usable web app manifest found on page.

Current page does not respond with a 200 when offline

If you're building a Progressive Web App, consider using a service worker so that your app can work offline. Learn more.

Installable

Does not use HTTPS

8 insecure requests 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.

Web app manifest does not meet the installability requirements

Browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement. Learn more. Failures: No manifest was fetched.

Osv.dev Mobile Accessibility: 85/100

Quick overview:

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.

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.

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.

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 tests

www.osv.com
www.osv.net
www.osv.org
www.osv.info
www.osv.biz
www.osv.us
www.osv.mobi
www.sv.dev
www.osv.dev
www.isv.dev
www.oisv.dev
www.iosv.dev
www.ksv.dev
www.oksv.dev
www.kosv.dev
www.lsv.dev
www.olsv.dev
www.losv.dev
www.psv.dev
www.opsv.dev
www.posv.dev
www.ov.dev
www.owv.dev
www.oswv.dev
www.owsv.dev
www.oev.dev
www.osev.dev
www.oesv.dev
www.odv.dev
www.osdv.dev
www.odsv.dev
www.ozv.dev
www.oszv.dev
www.ozsv.dev
www.oxv.dev
www.osxv.dev
www.oxsv.dev
www.oav.dev
www.osav.dev
www.oasv.dev
www.os.dev
www.osc.dev
www.osvc.dev
www.oscv.dev
www.osf.dev
www.osvf.dev
www.osfv.dev
www.osg.dev
www.osvg.dev
www.osgv.dev
www.osb.dev
www.osvb.dev
www.osbv.dev