teacupspuppies.com website review

159 files are served with short cache lifetimes, so returning visitors download them again (9.4 MB).

14 images could be 2.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 8.3 s faster on a phone.

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

About 852 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 4.5 s faster on a phone.

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

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

105 KiB could be saved by minifying CSS.

7 third-party services load with your homepage (YouTube, Google Tag Manager and birdeye.com and others), adding 1.4 MB and 673 ms of main-thread time.

YouTube costs a phone 483 ms of main-thread work and 982 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.

90 KiB could be saved by minifying JavaScript.

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

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

The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

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

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.

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.

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

Your largest element takes 23.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Welcome to South Florida’s original teacup puppy boutique! …”.

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

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

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

Real visitors see the first content after 2.4 s (75th percentile). Good is under 1.8 s.

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

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

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

Your homepage downloads 11.0 MB in 196 requests on a phone: images 7.6 MB (32), scripts 1.8 MB (72) and stylesheets 1.0 MB (75). Under 2 MB keeps phones on slow connections fast.

6 images weigh 5.0 MB together. On a phone connection a single image that size takes seconds.

7 images are downloaded at several times the size a phone draws them, for example halloween_yorkie_newborn_style_1400x800_72dpi.png at 1,400 px wide, shown at 332 px. Resized copies would save about 1.3 MB.

23 images (7.6 MB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

21 images further down the page (5.8 MB) 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 3.11 g of CO₂e: 373.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

24 links inside paragraphs rely on colour alone to stand out.

1 frame has no title, so screen-reader users cannot tell what it contains.

1 element has a tabindex above 0, which scrambles the keyboard order.

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

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

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

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

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

The homepage links to 131 pages on teacupspuppies.com and 42 external pages.

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.

Your homepage links to /pages/help, which answers with an error. Visitors hit a dead end and search engines drop it.

Your homepage links to 1 page by a URL that isn't its canonical one, for example /about-us/blog, whose canonical is /blog. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

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

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

1 link from your homepage to your own site is broken, for example https://www.teacupspuppies.com/pages/help/ (404).

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

No Content-Security-Policy header, the main browser-side defence against injected scripts.

The server only offers HTTP/1.1, so browsers open several connections and load files more slowly. Most hosts and CDNs turn on HTTP/2 with a setting.

Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

2 links go through two or more redirects, for example http://www.facebook.com/teacupspuppies.

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.

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

teacupspuppies.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.

teacupspuppies.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.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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 analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

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

The page uses urgency cues (a countdown or limited-time wording).

DMARC is set to p=none, so mail pretending to be teacupspuppies.com is still delivered. Add a report address, check the reports, then move to quarantine.

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 Analytics and Google Tag Manager (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 4 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 12 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.