myshapods.com website review

About 1.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 6.1 s faster on a phone.

28 files are served with short cache lifetimes, so returning visitors download them again (728 KiB).

25 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.0 s.

9 images could be 2.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

8 third-party services load with your homepage (Squarespace, Google Tag Manager and Facebook and others), adding 2.6 MB and 903 ms of main-thread time.

Your mobile performance score is 52. Pages that score under 90 lose visitors before the first paint.

Polyfills for old browsers add 149 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 600 ms faster on a phone.

About 134 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 610 ms faster on a phone.

109 KiB could be saved by minifying JavaScript.

Squarespace costs a phone 536 ms of main-thread work and 1.3 MB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

A phone's processor spends 2.8 s on main-thread work while loading, 1.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

The page has 2,334 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

Other Google APIs/SDKs costs a phone 45 ms of main-thread work and 503 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

9 long tasks block the main thread while loading, the longest for 157 ms. During a long task the page ignores taps.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

The first text or image appears after 7.6 s on a phone. Good is under 1.8 s.

Your largest element takes 25.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

The page becomes fully interactive after 25.7 s. Good is under 3.8 s.

Visually, the page fills in at 10.8 s (Speed Index). Good is under 3.4 s.

Scripts block taps and scrolling for 215 ms in total while the page loads. Good is under 200 ms.

1 image have no width and height attributes, so the layout jumps as each one loads.

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 6.0 MB in 154 requests on a phone: images 2.7 MB (14), scripts 2.6 MB (78) and fonts 238 KiB (10). Under 2 MB keeps phones on slow connections fast.

Mysha+Gradient+Grain+Dark.png weighs 530 KiB. On a phone connection a single image that size takes seconds.

Mysha+Gradient+Grain+Dark.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

By the Sustainable Web Design model, a visit to your homepage emits about 1.70 g of CO₂e: 204.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

13 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

1 element hidden from screen readers can still receive keyboard focus.

Some lists contain elements other than list items, which screen readers announce wrongly.

1 image has no alt text, which hurts accessibility and image search.

1 visible link has no text or label, so screen readers cannot say where it goes.

ARIA role should be appropriate for the element: 8 elements on the page fail this check, rated minor by axe-core.

Headings skip levels (h1 → h4, h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.

Your title is only 5 characters: “mysha”. Between 30 and 65 characters leaves room to say what you do and for whom.

Structured data found (LocalBusiness and WebSite) but with 2 problems, for example “WebSite: image is not an absolute URL ("//images.squarespace-cdn.com/content/v1/608242a4974f34647eb…”.

The homepage links to 26 pages on myshapods.com and 8 external pages.

Your Organization JSON-LD is missing name, url, logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

There is no https://myshapods.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

https://myshapods.com/home declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

https://myshapods.com/referral, https://myshapods.com/credits, https://myshapods.com/privacy, https://myshapods.com/terms and https://myshapods.com/guidelines are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

/ and https://myshapods.com/home all use the title “mysha”. Search engines can't tell which page to show for a search, so each competes with the others.

https://myshapods.com/terms has no meta description, so Google writes the search snippet from whatever text it finds.

https://myshapods.com/referral, https://myshapods.com/careers and https://myshapods.com/credits have no <h1> headline, so visitors and search engines get no clear main topic.

https://myshapods.com/quiz, https://myshapods.com/events and https://myshapods.com/contact have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

We fetched 13 pages linked from your homepage and read each the way a search engine does.

6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 401 ()”.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

The homepage shows no opening hours. If customers visit or call, show when.

There is no form on the homepage, so every lead has to click through to another page first.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 1,460 words of visible text.

Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager and Meta Pixel (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

Opening the homepage sets 7 cookies, 1 of them by other companies (measured from a US location before any click).

No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

Loading the homepage contacts 28 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.