Sulloway.org Test Results

Sulloway.org Mobile Performance: 100/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
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
7 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
Serve images in next-gen formats
Potential savings of 35 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.

Sulloway.org Mobile SEO: 67/100
Quick overview:
Crawling and Indexing
To appear in search results, crawlers need access to your app.
robots.txt is not valid
157 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 about robots.txt.
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Document doesn't have a `<title>` element
The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. Learn more about document titles.
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.

Sulloway.org Mobile Best Practices: 66/100
Quick overview:
Trust and Safety
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.
Does not use HTTPS
10 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.
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
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.
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.
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
Sulloway.org Mobile Accessibility: 30/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.
Document doesn't have a `<title>` element
The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. Learn more about document titles.
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.
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.
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.
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.
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.
Similar tests
www.sulloway.com
www.sulloway.net
www.sulloway.org
www.sulloway.info
www.sulloway.biz
www.sulloway.us
www.sulloway.mobi
www.ulloway.org
www.sulloway.org
www.wulloway.org
www.swulloway.org
www.wsulloway.org
www.eulloway.org
www.seulloway.org
www.esulloway.org
www.dulloway.org
www.sdulloway.org
www.dsulloway.org
www.zulloway.org
www.szulloway.org
www.zsulloway.org
www.xulloway.org
www.sxulloway.org
www.xsulloway.org
www.aulloway.org
www.saulloway.org
www.asulloway.org
www.slloway.org
www.sylloway.org
www.suylloway.org
www.syulloway.org
www.shlloway.org
www.suhlloway.org
www.shulloway.org
www.sjlloway.org
www.sujlloway.org
www.sjulloway.org
www.silloway.org
www.suilloway.org
www.siulloway.org
www.suloway.org
www.suploway.org
www.sulploway.org
www.suplloway.org
www.suoloway.org
www.suloloway.org
www.suolloway.org
www.sukloway.org
www.sulkloway.org
www.suklloway.org
www.sulpoway.org
www.sullpoway.org
www.sulooway.org
www.sullooway.org
www.sulkoway.org
www.sullkoway.org
www.sullway.org
www.sulliway.org
www.sulloiway.org
www.sullioway.org
www.sullkway.org
www.sullokway.org
www.sulllway.org
www.sullolway.org
www.sullloway.org
www.sullpway.org
www.sullopway.org
www.sulloay.org
www.sulloqay.org
www.sullowqay.org
www.sulloqway.org
www.sulloaay.org
www.sullowaay.org
www.sulloaway.org
www.sullosay.org
www.sullowsay.org
www.sullosway.org
www.sulloeay.org
www.sulloweay.org
www.sulloeway.org
www.sullowy.org
www.sullowqy.org
www.sullowaqy.org
www.sullowwy.org
www.sullowawy.org
www.sullowway.org
www.sullowsy.org
www.sullowasy.org
www.sullowzy.org
www.sullowazy.org
www.sullowzay.org
www.sullowa.org
www.sullowat.org
www.sullowayt.org
www.sullowaty.org
www.sullowag.org
www.sullowayg.org
www.sullowagy.org
www.sullowah.org
www.sullowayh.org
www.sullowahy.org
www.sullowau.org
www.sullowayu.org
www.sullowauy.org
Last Tested: