fureverflame.com website review

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

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

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

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

About 28 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.

3 third-party services load with your homepage (Shopify, cloudfront.net and shop.app), adding 78 KiB and 44 ms of main-thread time.

1 long task block the main thread while loading, the longest for 50 ms. During a long task the page ignores taps.

5 files are served with short cache lifetimes, so returning visitors download them again (13 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.

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

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.

Dog.jpg 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 0.50 g of CO₂e: 60.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

4 elements hidden from screen readers can still receive keyboard focus.

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.

Headings should not be empty: 4 elements on the page fail this check, rated minor by axe-core.

Your title is 67 characters, so Google will cut it off around 60: “Furever Flame | Pet Memorials & Emergency Preparedness with Purpose”.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

The homepage links to 56 pages on fureverflame.com and 10 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

Your homepage links to /collections/digital-resources/products/pet-sitter-instruction-card-copy, which answers with an error. Visitors hit a dead end and search engines drop it.

/collections/pet-essentials, /collections/digital-resources, /blogs/furever-flame-chronicles, /blogs/news and /collections/digital-resources/products/pet-sitter-instruction-card have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 4 pages by a URL that isn't their canonical one, for example /collections/pet-essentials/products/memorial-box, whose canonical is /products/memorial-box. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/pages/contact has no <h1> headline, so visitors and search engines get no clear main topic.

/collections/digital-resources and /pages/contact took over 3 s to send their HTML from our server.

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

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

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

1 link go through two or more redirects, for example https://www.fureverflame.com/account.

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.

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

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

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

The homepage carries about 726 words of visible text.

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

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 Meta Pixel, Pinterest Tag and TikTok 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 12 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 9 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.