Seltzer.org Test Results

Seltzer.org Mobile Performance: 99/100
Quick overview:
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
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
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.
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
Serve static assets with an efficient cache policy
5 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.

Seltzer.org Mobile SEO: 100/100
Quick overview:

Seltzer.org Mobile Best Practices: 69/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.
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
User Experience
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.
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
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.
Seltzer.org Mobile Accessibility: 77/100
Quick overview:
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
List items (`<li>`) are not contained within `<ul>`, `<ol>` or `<menu>` parent elements.
Screen readers require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.
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.
Form elements do not have associated labels
Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element 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.
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.seltzer.com
www.seltzer.net
www.seltzer.org
www.seltzer.info
www.seltzer.biz
www.seltzer.us
www.seltzer.mobi
www.eltzer.org
www.seltzer.org
www.weltzer.org
www.sweltzer.org
www.wseltzer.org
www.eeltzer.org
www.seeltzer.org
www.eseltzer.org
www.deltzer.org
www.sdeltzer.org
www.dseltzer.org
www.zeltzer.org
www.szeltzer.org
www.zseltzer.org
www.xeltzer.org
www.sxeltzer.org
www.xseltzer.org
www.aeltzer.org
www.saeltzer.org
www.aseltzer.org
www.sltzer.org
www.swltzer.org
www.sewltzer.org
www.ssltzer.org
www.sesltzer.org
www.sseltzer.org
www.sdltzer.org
www.sedltzer.org
www.srltzer.org
www.serltzer.org
www.sreltzer.org
www.setzer.org
www.septzer.org
www.selptzer.org
www.sepltzer.org
www.seotzer.org
www.selotzer.org
www.seoltzer.org
www.sektzer.org
www.selktzer.org
www.sekltzer.org
www.selzer.org
www.selrzer.org
www.seltrzer.org
www.selrtzer.org
www.selfzer.org
www.seltfzer.org
www.selftzer.org
www.selgzer.org
www.seltgzer.org
www.selgtzer.org
www.selyzer.org
www.seltyzer.org
www.selytzer.org
www.selter.org
www.seltxer.org
www.seltzxer.org
www.seltxzer.org
www.seltser.org
www.seltzser.org
www.seltszer.org
www.seltaer.org
www.seltzaer.org
www.seltazer.org
www.seltzr.org
www.seltzwr.org
www.seltzewr.org
www.seltzwer.org
www.seltzsr.org
www.seltzesr.org
www.seltzdr.org
www.seltzedr.org
www.seltzder.org
www.seltzrr.org
www.seltzerr.org
www.seltzrer.org
www.seltze.org
www.seltzee.org
www.seltzere.org
www.seltzeer.org
www.seltzed.org
www.seltzerd.org
www.seltzef.org
www.seltzerf.org
www.seltzefr.org
www.seltzet.org
www.seltzert.org
www.seltzetr.org
Last Tested: