flareshack.com website review

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

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

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

3 third-party services load with your homepage (JSDelivr CDN, Cloudflare CDN and Shopify), adding 2.5 MB and 24 ms of main-thread time.

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

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

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

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

About 23 KiB of JavaScript is downloaded but never used on this page.

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.

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

11 images 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.

2 images weigh 5.5 MB together. On a phone connection a single image that size takes seconds.

Your homepage downloads 4.9 MB in 166 requests on a phone: images 3.6 MB (40), other files 707 KiB (66) and fonts 285 KiB (6). Under 2 MB keeps phones on slow connections fast.

8 images (6.2 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.

8 images further down the page (4.1 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 1.39 g of CO₂e: 167.3 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.

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

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

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

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

Your title is 70 characters, so Google will cut it off around 60: “Flare Shack - Ultra Soft Anxiety Relieving Calming Bed for Dogs & Pets”.

Your meta description is 167 characters; Google truncates after about 160, so the end of your pitch is cut.

Structured data found (BreadcrumbList, Organization, Product and WebSite) but with 1 problem, for example “Organization: sameAs is an empty list”.

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

Your <h1> is empty.

The homepage links to 28 pages on flareshack.com and 1 external page.

/policies/shipping-policy, /policies/refund-policy, /policies/privacy-policy and /policies/terms-of-service have no meta description, so Google writes the search snippet from whatever text it finds.

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

HSTS is set, but max-age is 91 days; one year is the recommended minimum.

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.

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

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

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

DMARC is set to p=none, so mail pretending to be flareshack.com is still delivered. Reports are on, so moving to quarantine is the next step.

We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

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.

Opening the homepage sets 5 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 4 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.