Website review, no card needed

eliteflower.com logo

eliteflower.com website review

Visit site (opens in a new tab)Reviewed 31 October 202634 issues · 80 checks

This review found 34 issues worth fixing on eliteflower.com, 15 of them high impact, across 80 checks. The most urgent: improve image delivery. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
3.5 s2.7 sMay 9Oct 243.2 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.9 s
May 16, 20262.8 s
May 23, 20263.1 s
May 30, 20263.1 s
Jun 6, 20263.0 s
Jun 13, 20263.2 s
Jun 20, 20263.1 s
Jun 27, 20263.0 s
Jul 4, 20263.1 s
Jul 11, 20263.0 s
Jul 18, 20263.0 s
Jul 25, 20263.2 s
Aug 1, 20263.2 s
Aug 8, 20263.3 s
Aug 15, 20263.4 s
Aug 22, 20263.1 s
Aug 29, 20263.0 s
Sep 5, 20263.0 s
Sep 12, 20263.0 s
Sep 19, 20263.2 s
Sep 26, 20263.4 s
Oct 3, 20263.3 s
Oct 10, 20263.3 s
Oct 17, 20263.2 s
Oct 24, 20263.2 s
Real-visitor tap response (INP)75th percentile, phones
119 ms91 msMay 9Oct 24114 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 202699 ms
May 16, 2026100 ms
May 23, 2026102 ms
May 30, 2026110 ms
Jun 6, 2026104 ms
Jun 13, 2026112 ms
Jun 20, 2026111 ms
Jun 27, 2026111 ms
Jul 4, 2026115 ms
Jul 11, 2026111 ms
Jul 18, 2026104 ms
Jul 25, 202698 ms
Aug 1, 202694 ms
Aug 8, 202696 ms
Aug 15, 2026103 ms
Aug 22, 2026104 ms
Aug 29, 2026106 ms
Sep 5, 2026106 ms
Sep 12, 202699 ms
Sep 19, 2026103 ms
Sep 26, 2026101 ms
Oct 3, 2026101 ms
Oct 10, 2026111 ms
Oct 17, 2026116 ms
Oct 24, 2026114 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of eliteflower.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. eliteflower.com at 1.2 s1.2 s
  2. eliteflower.com at 2.3 s2.3 s
  3. eliteflower.com at 3.5 s3.5 s
  4. eliteflower.com at 4.7 s4.7 s
  5. eliteflower.com at 5.9 s5.9 s
  6. eliteflower.com at 7.0 s7.0 s
  7. eliteflower.com at 8.2 s8.2 s
  8. eliteflower.com at 9.4 s9.4 s

Speed

7 to fix57
  • Improve image delivery

    3.4 s · 4.0 MB

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

  • Render-blocking requests

    2.2 s

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

  • Font display

    1.1 s

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

  • Mobile performance score: 57

    57/100

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

  • Reduce unused CSS

    600 ms · 114 KiB

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

  • 3 third-party services on the page

    3 third-party services load with your homepage (Bootstrap CDN, Google Fonts and Instagram), adding 2.4 MB and 3 ms of main-thread time.

  • Instagram adds 0 ms

    0 ms

    Instagram costs a phone 0 ms of main-thread work and 2.3 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.

  • Use efficient cache lifetimes

    234 KiB

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

  • Document request latency

    149 KiB

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

  • 1 long task on the main thread

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

  • Chained critical requests

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

  • Minify CSS

    4 KiB

    4 KiB could be saved by minifying CSS.

  • Minify JavaScript

    3 KiB

    3 KiB could be saved by minifying JavaScript.

2 checks passed
  • Main-thread work: 1.1 s

    A phone's processor spends 1.1 s on main-thread work while loading, 359 ms of it running JavaScript. That is comfortably low.

  • Server response: 203 ms

    203 ms

    Your server sent the HTML in 203 ms, well inside Google's 600 ms guideline.

Core Web Vitals

9 to fix67
  • Fails Core Web Vitals for real visitors

    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.

  • Real-user LCP: 4.2 s

    4.2 s

    Real visitors wait 4.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user FCP: 3.4 s

    3.4 s

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

  • Real-user TTFB: 2.2 s

    2.2 s

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

  • Largest Contentful Paint: 22.2 s

    22.2 s

    Your largest element takes 22.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below. Most of its time is resource load delay (8.9 s).

  • Speed Index: 15.1 s

    15.1 s

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

  • Time to Interactive: 23.4 s

    23.4 s

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

  • First Contentful Paint: 3.9 s

    3.9 s

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

  • 4 images without width and height

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

  • Tap response (INP) got 16% slower for real visitors

    +16%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 99 ms to 114 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) got 12% slower for real visitors

    +12%

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

4 checks passed
  • Real-user INP: 111 ms

    111 ms

    Real visitors wait 111 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.00

    0.00

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

  • Cumulative Layout Shift: 0.006

    0.006

    The layout barely moves while loading (CLS 0.006, good is under 0.1).

  • Total Blocking Time: 15 ms

    15 ms

    Scripts block the page for only 15 ms while loading. Good is under 200 ms.

Images and page weight

1 to fix70
  • Page weight: 6.7 MB in 62 requests

    6.7 MB

    Your homepage downloads 6.7 MB in 62 requests on a phone: images 5.9 MB (14), HTML 223 KiB (1) and fonts 220 KiB (4). Under 2 MB keeps phones on slow connections fast.

  • About 1.9 g of CO₂ per visit

    1.90 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

4 to fixGoogle 9395
  • All page content should be contained by landmarks (39 elements)

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • Page should contain a level-one heading (1 element)

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

  • 2 links without text

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

  • Headings skip levels

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

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

2 checks passed
  • Every image has alt text

    All 25 images in the HTML carry an alt attribute.

  • 36 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 41 WCAG 2.2 A/AA and best-practice rules on the phone render: 36 passed and 5 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 9273
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • No structured data

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

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 83 internal links, 13 external

    The homepage links to 83 pages on eliteflower.com and 13 external pages.

4 checks passed
  • Title: 31 characters

    Your title is a healthy 31 characters: “The Elite Flower – By Hannaford”.

  • Canonical URL set

    The canonical URL is https://eliteflower.com/.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://eliteflower.com/wp-sitemap.xml.

AI search readiness

1 to fix88
  • No Organization structured data

    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.

  • No llms.txt

    There is no https://eliteflower.com/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.

2 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Text is in the HTML

    Your server sends the page's text in the HTML (584 words), so crawlers that don't run JavaScript still read it.

Other pages

4 to fix60
  • 2 linked pages are broken

    Your homepage links to https://eliteflower.com/index.php/muse-collection and https://eliteflower.com/index.php/preserved-timeless, which answer with an error. Visitors hit a dead end and search engines drop them.

  • 12 pages without a meta description

    https://eliteflower.com/index.php/about-us, https://eliteflower.com/index.php/our-standards, https://eliteflower.com/index.php/elite-farms, https://eliteflower.com/index.php/our-flowers, https://eliteflower.com/index.php/we-care and https://eliteflower.com/index.php/certifications and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://eliteflower.com/index.php/home-6, whose canonical is https://eliteflower.com/index.php/home-6-2-3-2. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 12 pages without an H1

    https://eliteflower.com/index.php/about-us, https://eliteflower.com/index.php/our-standards, https://eliteflower.com/index.php/elite-farms, https://eliteflower.com/index.php/our-flowers, https://eliteflower.com/index.php/we-care and https://eliteflower.com/index.php/certifications and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 7 pages slow to respond

    https://eliteflower.com/index.php/elite-farms, https://eliteflower.com/index.php/our-flowers, https://eliteflower.com/index.php/we-care, https://eliteflower.com/index.php/certifications, https://eliteflower.com/index.php/contact and https://eliteflower.com/index.php/our-roses and 1 other took over 3 s to send their HTML from our server.

  • 14 internal pages checked

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

3 checks passed
  • Titles are unique

    Every page we checked has its own title.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 12 pages that loaded have a <title>.

Best practices

1 to fixGoogle 10093
  • 8 small tap targets

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

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix70
  • Thin social proof

    Social proof on the homepage: 1 customer or partner logo. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No analytics detected

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

  • No direct contact details

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

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

  • No risk reducer

    No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

  • About 359 words of copy

    The homepage carries about 359 words of visible text.

2 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “CONTACT”.

  • 9 calls to action

    The homepage has 9 calls to action, for example “Contact” and “contact”.

Privacy and tracking

  • No consent tool detected

    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.

  • 5 other companies contacted

    Loading the homepage contacts 5 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at eliteflower.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
WordPress
Framework
jQuery
Hosting
GoDaddy

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 34 issues on eliteflower.com, including 16 speed issues, 4 SEO issues and 3 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25