divinefloral.com website review

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

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

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

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

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

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

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

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

7 third-party services load with your homepage (FullStory, Google Tag Manager and Shopify and others), adding 684 KiB and 370 ms of main-thread time.

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

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

4 KiB could be saved by minifying JavaScript.

Your largest element takes 8.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “autumn flower arrangement on fall decorated table”.

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

Visually, the page fills in at 4.0 s (Speed Index). Good is under 3.4 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.

Your homepage downloads 2.3 MB in 209 requests on a phone: other files 736 KiB (89), images 708 KiB (22) and scripts 563 KiB (56). Under 2 MB keeps phones on slow connections fast.

homepageBannerMetadata_Image_1758311559756.png 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).

1 image (42 KiB) is 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.

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

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

1 tap target is too small or too close together to hit reliably with a finger.

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

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

Structured data found (FAQPage, LocalBusiness, Organization and WebSite) but with 1 problem, for example “LocalBusiness: logo is not an absolute URL ("//divinefloral.com/cdn/shop/files/Divine_Floral_Gifts_…”.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 1,245 pages on divinefloral.com and 8 external pages.

Your homepage links to https://divinefloral.com/pages/news, which answers with an error. Visitors hit a dead end and search engines drop it.

https://divinefloral.com/pages/reminder-service and https://divinefloral.com/pages/about-us use the same meta description. A description written for each page earns more clicks.

https://divinefloral.com/collections/balloon-bouquets and https://divinefloral.com/pages/about-us have no <h1> headline, so visitors and search engines get no clear main topic.

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

Social proof on the homepage: 32 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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

The homepage carries about 5,907 words of visible text.

Before a visitor clicks anything, the page loads FullStory, Google Ads, 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 8 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 13 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.