Obis.org Site Title

Ocean Biodiversity Information System

Obis.org Meta Description

OBIS, the Ocean Biodiversity Information System, is a global open-access data and information clearing-house on marine biodiversity for science, conservation and sustainable development.

Obis.org Test Results

Obis.org Mobile Performance: 45/100
Quick overview:
First Meaningful Paint
7.1 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric.
Time to Interactive
10.7 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
210 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.
Avoid serving legacy JavaScript to modern browsers
Potential savings of 29 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 how to use modern JavaScript
Avoid multiple page redirects
Potential savings of 630 ms
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Eliminate render-blocking resources
Potential savings of 5,820 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn how to eliminate render-blocking resources.
Reduce unused JavaScript
Potential savings of 601 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.
Avoid large layout shifts
1 layout shift found
These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLS
Serve images in next-gen formats
Potential savings of 1,914 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more about modern image formats.
Enable text compression
Potential savings of 726 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more about text compression.
Largest Contentful Paint element
16,940 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element
Minify CSS
Potential savings of 64 KiB
Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.
Properly size images
Potential savings of 652 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.
Minimize main-thread work
2.7 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work
Efficiently encode images
Potential savings of 578 KiB
Optimized images load faster and consume less cellular data. Learn how to efficiently encode images.
Minify JavaScript
Potential savings of 102 KiB
Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.
Reduce unused CSS
Potential savings of 316 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.
Reduce JavaScript execution time
1.4 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.
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 about adopting passive event listeners.
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 enormous network payloads
Total size was 4,451 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
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 how to set image dimensions
Defer offscreen images
Potential savings of 173 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.
Serve static assets with an efficient cache policy
40 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.

Obis.org Mobile SEO: 92/100
Quick overview:
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 about the `alt` attribute.

Obis.org Mobile Best Practices: 83/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.
Obis.org Mobile Accessibility: 70/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.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` are missing some or all of those required children.
Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.
ARIA input fields do not have accessible names
When an input field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about input field labels.
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 about the `lang` attribute.
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 about the `alt` attribute.
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.
Select elements do not have associated label elements.
Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.
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.
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 sites
Similar tests
www.obis.com
www.obis.net
www.obis.org
www.obis.info
www.obis.biz
www.obis.us
www.obis.mobi
www.bis.org
www.obis.org
www.ibis.org
www.oibis.org
www.iobis.org
www.kbis.org
www.okbis.org
www.kobis.org
www.lbis.org
www.olbis.org
www.lobis.org
www.pbis.org
www.opbis.org
www.pobis.org
www.ois.org
www.ovis.org
www.obvis.org
www.ovbis.org
www.ogis.org
www.obgis.org
www.ogbis.org
www.ohis.org
www.obhis.org
www.ohbis.org
www.onis.org
www.obnis.org
www.onbis.org
www.obs.org
www.obus.org
www.obius.org
www.obuis.org
www.objs.org
www.obijs.org
www.objis.org
www.obks.org
www.obiks.org
www.obkis.org
www.obos.org
www.obios.org
www.obois.org
www.obi.org
www.obiw.org
www.obisw.org
www.obiws.org
www.obie.org
www.obise.org
www.obies.org
www.obid.org
www.obisd.org
www.obids.org
www.obiz.org
www.obisz.org
www.obizs.org
www.obix.org
www.obisx.org
www.obixs.org
www.obia.org
www.obisa.org
www.obias.org
Last Tested: