graceframe.com website review

Your mobile performance score is 18 (desktop: 23). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

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

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

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

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

Facebook costs a phone 283 ms of main-thread work and 318 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.

Klaviyo costs a phone 132 ms of main-thread work and 336 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.

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

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

11 images could be 119 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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

23 KiB could be saved by minifying JavaScript.

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

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

For real visitors the layout shifts by 0.92 (75th percentile). Good is under 0.1.

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

The layout shifts by 0.933 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

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

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

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

Real visitors wait 971 ms for your server to start answering (75th percentile). Good is under 800 ms.

36 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-17, real Chrome visitors' largest content (lcp) went from 2.1 s to 2.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 4.1 MB in 229 requests on a phone: scripts 2.8 MB (75), images 921 KiB (76) and fonts 254 KiB (6). Under 2 MB keeps phones on slow connections fast.

11 images further down the page (373 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

11 buttons have no accessible name, so screen readers announce just “button”.

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

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

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

All page content should be contained by landmarks: 34 elements on the page fail this check, rated moderate by axe-core.

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

24 visible links have no text or label, so screen readers cannot say where they go.

6 form fields have no label, so screen readers announce an empty box and autofill guesses.

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is 70 characters, so Google will cut it off around 60: “Quilting Tools & Accessories | Quilting Essentials | The Grace Company”.

Structured data found (Organization and WebSite) but with 1 problem, for example “Organization: missing name”.

7 links have no real href, so search engines can't follow them.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 139 pages on graceframe.com and 11 external pages.

Your Organization JSON-LD is missing name, sameAs (social profiles) and description. 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 /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.

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

3 images failed to load on a phone, for example https://jelly.mdhv.io/v1/star.gif?pid=TGU7npdwCu3Jf9dVV8ysclnCAimH&src=mh&evt=hi.

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

2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

5 errors were logged to the browser console while the page loaded, for example “Unexpected identifier 'https'”.

Requests the geolocation permission on page load.

Chrome logged issues while loading the page (“Cookie”).

No Strict-Transport-Security header, so browsers may still try plain http first on a return visit.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

graceframe.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

graceframe.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

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.

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.

The homepage carries about 942 words of visible text.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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