floralamer.com website review

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

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

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

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

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

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

8 third-party services load with your homepage (Shopify, avada.io and enhencer.com and others), adding 2.0 MB and 420 ms of main-thread time.

Shopify costs a phone 335 ms of main-thread work and 1.8 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,978 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

12 KiB could be saved by minifying JavaScript.

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

6 files are served with short cache lifetimes, so returning visitors download them again (25 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 11.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “A THOUGHTFUL DETAIL FLM Welcomes you to a world of beautifu…”.

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

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

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

Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 2.9 s to 2.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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 5.2 MB in 366 requests on a phone: other files 2.0 MB (209), images 1.6 MB (18) and scripts 1.2 MB (84). Under 2 MB keeps phones on slow connections fast.

Luxury_Red_Rose_Bouquet_in_Black_Wrap.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 is downloaded at several times the size a phone draws it, for example Luxury_Red_Rose_Bouquet_in_Black_Wrap.png at 1,199 px wide, shown at 390 px. Resized copies would save about 9 KiB.

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

ARIA roles used must conform to valid values: 2 elements on the page fail this check, rated critical by axe-core.

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

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

Elements must only use permitted ARIA attributes: 2 elements on the page fail this check, rated serious by axe-core.

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

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

Alternative text of images should not be repeated as text: 12 elements on the page fail this check, rated minor by axe-core.

1 form field has no label, so screen readers announce an empty box and autofill guesses.

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

Elements with visible text labels do not have matching accessible names. (2 elements).

Your title is 76 characters, so Google will cut it off around 60: “Flower Delivery in Dubai | Luxury Roses & Gifts – Flora La Mer – Flora Lamer”.

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

Your <h1> is empty.

The homepage links to 95 pages on floralamer.com and 8 external pages.

https://floralamer.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://floralamer.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://floralamer.com/customer_authentication/redirect has no meta description, so Google writes the search snippet from whatever text it finds.

https://floralamer.com/customer_authentication/redirect has no <h1> headline, so visitors and search engines get no clear main topic.

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

2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://fonts.googleapis.com/css2?family=' from origin 'https://floralamer.com' has been b…”.

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

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

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