trishscully.com website review

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

14 images could be 611 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 800 ms faster on a phone.

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

8 third-party services load with your homepage (Google Tag Manager, Shopify and Klaviyo and others), adding 1.2 MB and 832 ms of main-thread time.

2 files block the first paint until they finish downloading. Deferring or inlining them could save about 450 ms.

Google Tag Manager costs a phone 357 ms of main-thread work and 343 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.

Shopify costs a phone 322 ms of main-thread work and 604 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.

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

About 217 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 250 ms faster on a phone.

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

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

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

Polyfills for old browsers add 27 KiB JavaScript that modern phones do not need.

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

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.

3 KiB could be saved by minifying CSS.

Your largest element takes 7.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 17.2 s. Good is under 3.8 s.

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

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

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

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 105 ms to 104 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 17.9 MB in 304 requests on a phone: media 12.9 MB (1), images 1.9 MB (32) and other files 1.6 MB (157). Under 2 MB keeps phones on slow connections fast.

Screenshot_2026-10-08_at_11.14.55_AM_637c7d67-1316-4396-9166 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 5.08 g of CO₂e: 609.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

5 tap targets are too small or too close together to hit reliably with a finger.

3 images have no alt text, which hurts accessibility and image search.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

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

The homepage links to 246 pages on trishscully.com and 5 external pages.

There is no https://trishscully.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://trishscully.com/collections/girls-clothes, https://trishscully.com/collections/girls-dressup, https://trishscully.com/collections/girls-accessories and https://trishscully.com/collections/girls-shoes have no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 15 pages linked from your homepage (of 99 found) and read each the way a search engine does.

11 of 44 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

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 394 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Xandr (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 12 cookies, 2 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 24 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.