Submers.org Site Title

Hauptseite – SubmersWiki

Submers.org Test Results

Submers.org Mobile Performance: 52/100
Quick overview:
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Eliminate render-blocking resources
Potential savings of 5,730 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.
Avoid serving legacy JavaScript to modern browsers
Potential savings of 100 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
Enable text compression
Potential savings of 773 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more about text compression.
Avoid multiple page redirects
Potential savings of 600 ms
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Minify JavaScript
Potential savings of 233 KiB
Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.
Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
A `<meta name="viewport">` not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn more about using the viewport meta tag. No `<meta name="viewport">` tag found
Largest Contentful Paint element
9,440 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element
Minimize main-thread work
2.8 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
Reduce unused JavaScript
Potential savings of 654 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.
Reduce unused CSS
Potential savings of 26 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.
Avoid `document.write()`
For users on slow connections, external scripts dynamically injected via `document.write()` can delay page load by tens of seconds. Learn how to avoid document.write().
Serve static assets with an efficient cache policy
83 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
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 25 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 images in next-gen formats
Potential savings of 125 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.
Minify CSS
Potential savings of 6 KiB
Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.
Efficiently encode images
Potential savings of 86 KiB
Optimized images load faster and consume less cellular data. Learn how to efficiently encode images.
Time to Interactive
11.0 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.

Submers.org Mobile SEO: 82/100
Quick overview:
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
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.
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.

Submers.org Mobile Best Practices: 24/100
Quick overview:
Trust and Safety
Does not use HTTPS
91 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 about HTTPS.
Does not redirect HTTP traffic to HTTPS
Make sure that you redirect all HTTP traffic to HTTPS in order to enable secure web features for all your users. Learn more.
Browser Compatibility
Page lacks the HTML doctype, thus triggering quirks-mode
Specifying a doctype prevents the browser from switching to quirks-mode. Learn more about the doctype declaration. Document must contain a doctype
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 about this errors in console diagnostic audit
Uses third-party cookies
1 cookie found
Chrome is moving towards a new experience that allows users to choose to browse without third-party cookies. Learn more about third-party cookies.
Uses deprecated APIs
2 warnings found
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
Issues were logged in the `Issues` panel in Chrome Devtools
Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.
User Experience
Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
A `<meta name="viewport">` not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn more about using the viewport meta tag. No `<meta name="viewport">` tag found
Document doesn't use legible font sizes
Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px. Learn more about legible font sizes. Text is illegible because there's no viewport meta tag optimized for mobile screens.
Serves images with low resolution
Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn how to provide responsive images.
Submers.org Mobile Accessibility: 76/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.
`<frame>` or `<iframe>` elements do not have a title
Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.
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.
`<td>` elements in a large `<table>` do not have table headers.
Screen readers have features to make navigating tables easier. Ensuring that `<td>` elements in a large table (3 or more cells in width and height) have an associated table header may improve the experience for screen reader users. Learn more about table headers.
Tables do not use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
Screen readers have features to make navigating tables easier. Ensuring that tables use the actual caption element instead of cells with the `colspan]` attribute may improve the experience for screen reader users. [Learn more about captions.
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.
Best practices
These items highlight common accessibility best practices.
Touch targets do not have sufficient size or spacing.
Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.
Similar tests
www.submers.com
www.submers.net
www.submers.org
www.submers.info
www.submers.biz
www.submers.us
www.submers.mobi
www.ubmers.org
www.submers.org
www.wubmers.org
www.swubmers.org
www.wsubmers.org
www.eubmers.org
www.seubmers.org
www.esubmers.org
www.dubmers.org
www.sdubmers.org
www.dsubmers.org
www.zubmers.org
www.szubmers.org
www.zsubmers.org
www.xubmers.org
www.sxubmers.org
www.xsubmers.org
www.aubmers.org
www.saubmers.org
www.asubmers.org
www.sbmers.org
www.sybmers.org
www.suybmers.org
www.syubmers.org
www.shbmers.org
www.suhbmers.org
www.shubmers.org
www.sjbmers.org
www.sujbmers.org
www.sjubmers.org
www.sibmers.org
www.suibmers.org
www.siubmers.org
www.sumers.org
www.suvmers.org
www.subvmers.org
www.suvbmers.org
www.sugmers.org
www.subgmers.org
www.sugbmers.org
www.suhmers.org
www.subhmers.org
www.sunmers.org
www.subnmers.org
www.sunbmers.org
www.subers.org
www.subners.org
www.submners.org
www.subjers.org
www.submjers.org
www.subjmers.org
www.subkers.org
www.submkers.org
www.subkmers.org
www.submrs.org
www.submwrs.org
www.submewrs.org
www.submwers.org
www.submsrs.org
www.submesrs.org
www.submsers.org
www.submdrs.org
www.submedrs.org
www.submders.org
www.submrrs.org
www.submerrs.org
www.submrers.org
www.submes.org
www.submees.org
www.submeres.org
www.submeers.org
www.submeds.org
www.submerds.org
www.submefs.org
www.submerfs.org
www.submefrs.org
www.submets.org
www.submerts.org
www.submetrs.org
www.submer.org
www.submerw.org
www.submersw.org
www.submerws.org
www.submere.org
www.submerse.org
www.submerd.org
www.submersd.org
www.submerz.org
www.submersz.org
www.submerzs.org
www.submerx.org
www.submersx.org
www.submerxs.org
www.submera.org
www.submersa.org
www.submeras.org
Last Tested: