Moreincommon.com Site Title

We are More in Common

Moreincommon.com Test Results

Moreincommon.com Mobile Performance: 29/100
Quick overview:
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Reduce JavaScript execution time
4.5 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.
Preload Largest Contentful Paint image
Potential savings of 2,260 ms
If the LCP element is dynamically added to the page, you should preload the image in order to improve LCP. Learn more about preloading LCP elements.
Reduce the impact of third-party code
Third-party code blocked the main thread for 3,410 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn how to minimize third-party impact.
Reduce unused JavaScript
Potential savings of 724 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.
Serve images in next-gen formats
Potential savings of 4,597 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.
Some third-party resources can be lazy loaded with a facade
1 facade alternative available
Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required. Learn how to defer third-parties with a facade.
Reduce unused CSS
Potential savings of 83 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 multiple page redirects
Potential savings of 1,740 ms
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Minimize main-thread work
6.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 minimize main-thread work
Largest Contentful Paint element
17,800 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element
Efficiently encode images
Potential savings of 15 KiB
Optimized images load faster and consume less cellular data. Learn how to efficiently encode images.
Serve static assets with an efficient cache policy
25 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
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`.
Eliminate render-blocking resources
Potential savings of 0 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 enormous network payloads
Total size was 10,840 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
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.
Max Potential First Input Delay
1,350 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.
First Meaningful Paint
9.5 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
18.5 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.

Moreincommon.com Mobile SEO: 67/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. Description text is empty.
Links do not have descriptive text
1 link found
Descriptive link text helps search engines understand your content. Learn how to make links more accessible.
Crawling and Indexing
To appear in search results, crawlers need access to your app.
robots.txt is not valid
1 error 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.
Links are not crawlable
Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable

Moreincommon.com Mobile Best Practices: 72/100
Quick overview:
Trust and Safety
Does not use HTTPS
2 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.
General
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.
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
User Experience
Displays images with incorrect aspect ratio
Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.
Moreincommon.com Mobile Accessibility: 82/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 have `[alt]` attributes that are redundant text.
Informative elements should aim for short, descriptive alternative text. Alternative text that is exactly the same as the text adjacent to the link or image is potentially confusing for screen reader users, because the text will be read twice. Learn more about the `alt` attribute.
Buttons do not have an accessible name
When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.
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 `role="dialog"` or `role="alertdialog"` do not have accessible names.
ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.
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.
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.moreincommon.com
www.moreincommon.net
www.moreincommon.org
www.moreincommon.info
www.moreincommon.biz
www.moreincommon.us
www.moreincommon.mobi
www.oreincommon.com
www.moreincommon.com
www.noreincommon.com
www.mnoreincommon.com
www.nmoreincommon.com
www.joreincommon.com
www.mjoreincommon.com
www.jmoreincommon.com
www.koreincommon.com
www.mkoreincommon.com
www.kmoreincommon.com
www.mreincommon.com
www.mireincommon.com
www.moireincommon.com
www.mioreincommon.com
www.mkreincommon.com
www.mokreincommon.com
www.mlreincommon.com
www.molreincommon.com
www.mloreincommon.com
www.mpreincommon.com
www.mopreincommon.com
www.mporeincommon.com
www.moeincommon.com
www.moeeincommon.com
www.moreeincommon.com
www.moereincommon.com
www.modeincommon.com
www.mordeincommon.com
www.modreincommon.com
www.mofeincommon.com
www.morfeincommon.com
www.mofreincommon.com
www.moteincommon.com
www.morteincommon.com
www.motreincommon.com
www.morincommon.com
www.morwincommon.com
www.morewincommon.com
www.morweincommon.com
www.morsincommon.com
www.moresincommon.com
www.morseincommon.com
www.mordincommon.com
www.moredincommon.com
www.morrincommon.com
www.morerincommon.com
www.morreincommon.com
www.morencommon.com
www.moreuncommon.com
www.moreiuncommon.com
www.moreuincommon.com
www.morejncommon.com
www.moreijncommon.com
www.morejincommon.com
www.morekncommon.com
www.moreikncommon.com
www.morekincommon.com
www.moreoncommon.com
www.moreioncommon.com
www.moreoincommon.com
www.moreicommon.com
www.moreibcommon.com
www.moreinbcommon.com
www.moreibncommon.com
www.moreihcommon.com
www.moreinhcommon.com
www.moreihncommon.com
www.moreijcommon.com
www.moreinjcommon.com
www.moreimcommon.com
www.moreinmcommon.com
www.moreimncommon.com
www.moreinommon.com
www.moreinxommon.com
www.moreincxommon.com
www.moreinxcommon.com
www.moreindommon.com
www.moreincdommon.com
www.moreindcommon.com
www.moreinfommon.com
www.moreincfommon.com
www.moreinfcommon.com
www.moreinvommon.com
www.moreincvommon.com
www.moreinvcommon.com
www.moreincmmon.com
www.moreincimmon.com
www.moreincoimmon.com
www.moreinciommon.com
www.moreinckmmon.com
www.moreincokmmon.com
www.moreinckommon.com
www.moreinclmmon.com
www.moreincolmmon.com
www.moreinclommon.com
www.moreincpmmon.com
www.moreincopmmon.com
www.moreincpommon.com
www.moreincomon.com
www.moreinconmon.com
www.moreincomnmon.com
www.moreinconmmon.com
www.moreincojmon.com
www.moreincomjmon.com
www.moreincojmmon.com
www.moreincokmon.com
www.moreincomkmon.com
www.moreincomnon.com
www.moreincommnon.com
www.moreincomjon.com
www.moreincommjon.com
www.moreincomkon.com
www.moreincommkon.com
www.moreincommn.com
www.moreincommin.com
www.moreincommoin.com
www.moreincommion.com
www.moreincommkn.com
www.moreincommokn.com
www.moreincommln.com
www.moreincommoln.com
www.moreincommlon.com
www.moreincommpn.com
www.moreincommopn.com
www.moreincommpon.com
www.moreincommo.com
www.moreincommob.com
www.moreincommonb.com
www.moreincommobn.com
www.moreincommoh.com
www.moreincommonh.com
www.moreincommohn.com
www.moreincommoj.com
www.moreincommonj.com
www.moreincommojn.com
www.moreincommom.com
www.moreincommonm.com
www.moreincommomn.com
www.moreincommon.con
Last Tested: