Website review, no card needed

abcflora.com logo

abcflora.com website review

Visit site (opens in a new tab)Reviewed 31 October 202619 issues · 96 checks

This review found 19 issues worth fixing on abcflora.com, 3 of them high impact, across 96 checks. The most urgent: 4 text elements with low contrast. 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
2.1 s1.4 sMay 9Oct 241.5 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.0 s
May 16, 20261.8 s
May 23, 20261.7 s
May 30, 20261.8 s
Jun 6, 20261.6 s
Jun 13, 20261.8 s
Jun 20, 20261.6 s
Jun 27, 20261.5 s
Jul 4, 20261.6 s
Jul 11, 20261.6 s
Jul 18, 20261.7 s
Jul 25, 20261.8 s
Aug 1, 20261.9 s
Aug 8, 20262.0 s
Aug 15, 20262.0 s
Aug 22, 20261.9 s
Aug 29, 20261.9 s
Sep 5, 20261.7 s
Sep 12, 20261.7 s
Sep 19, 20261.7 s
Sep 26, 20261.6 s
Oct 3, 20261.6 s
Oct 10, 20261.7 s
Oct 17, 20261.6 s
Oct 24, 20261.5 s
Real-visitor tap response (INP)75th percentile, phones
110 ms78 msMay 9Oct 2497 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 202694 ms
May 16, 202693 ms
May 23, 202690 ms
May 30, 202693 ms
Jun 6, 202699 ms
Jun 13, 2026102 ms
Jun 20, 202697 ms
Jun 27, 202697 ms
Jul 4, 202697 ms
Jul 11, 202693 ms
Jul 18, 202693 ms
Jul 25, 202692 ms
Aug 1, 202682 ms
Aug 8, 202683 ms
Aug 15, 202684 ms
Aug 22, 202685 ms
Aug 29, 202695 ms
Sep 5, 2026106 ms
Sep 12, 2026102 ms
Sep 19, 2026106 ms
Sep 26, 2026104 ms
Oct 3, 2026105 ms
Oct 10, 2026105 ms
Oct 17, 2026102 ms
Oct 24, 202697 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 abcflora.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. abcflora.com at 0.4 s0.4 s
  2. abcflora.com at 0.8 s0.8 s
  3. abcflora.com at 1.1 s1.1 s
  4. abcflora.com at 1.5 s1.5 s
  5. abcflora.com at 1.9 s1.9 s
  6. abcflora.com at 2.3 s2.3 s
  7. abcflora.com at 2.6 s2.6 s
  8. abcflora.com at 3.0 s3.0 s

abcflora.com does not allow embedding, so this is Google's rendering of the page.

Speed

4 to fix70
  • Improve image delivery

    950 ms · 198 KiB

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

  • Mobile performance score: 70

    70/100

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

  • Use efficient cache lifetimes

    650 ms · 106 KiB

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

  • Reduce unused JavaScript

    450 ms · 82 KiB

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

  • 2 long tasks on the main thread

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

  • 5 third-party services on the page

    5 third-party services load with your homepage (cloudfront.net, Shopify and Cloudflare and others), adding 171 KiB and 87 ms of main-thread time.

  • Legacy JavaScript

    20 KiB

    Polyfills for old browsers add 20 KiB JavaScript that modern phones do not need.

  • Reduce unused CSS

    16 KiB

    About 16 KiB of CSS is downloaded but never applied on this page.

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

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

  • Minify JavaScript

    4 KiB

    4 KiB could be saved by minifying JavaScript.

2 checks passed
  • Main-thread work: 1.2 s

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

  • Server response: 6 ms

    6 ms

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

Core Web Vitals

4 to fix100
  • Largest Contentful Paint: 6.9 s

    6.9 s

    Your largest element takes 6.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Luxury flower bouquet”.

  • Time to Interactive: 6.9 s

    6.9 s

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

  • Speed Index: 5.3 s

    5.3 s

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

  • First Contentful Paint: 2.0 s

    2.0 s

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

  • Tap response (INP) held steady for real visitors

    +6%

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

9 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 1.4 s

    1.4 s

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

  • Real-user INP: 88 ms

    88 ms

    Real visitors wait 88 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.

  • Real-user FCP: 1.1 s

    1.1 s

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

  • Real-user TTFB: 662 ms

    662 ms

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

  • Largest content (LCP) got 17% faster for real visitors

    -17%

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

  • Total Blocking Time: 104 ms

    104 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix90
  • 3 images in older formats

    3 images (800 KiB) 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.

  • About 0.5 g of CO₂ per visit

    0.46 g

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

3 checks passed
  • Page weight: 1.6 MB in 119 requests

    1.6 MB

    Your homepage downloads 1.6 MB in 119 requests on a phone: other files 676 KiB (64), images 350 KiB (8) and scripts 348 KiB (38). That is a lean page.

  • 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 9795
  • 4 text elements with low contrast

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

  • All page content should be contained by landmarks (2 elements)

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

  • 14 links without text

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

  • 1 form field without a label

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

2 checks passed
  • Every image has alt text

    All 17 images in the HTML carry an alt attribute.

  • 48 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 2 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

1 to fixGoogle 9298
  • 3 links with vague text

    3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 143 internal links, 7 external

    The homepage links to 143 pages on abcflora.com and 7 external pages.

8 checks passed
  • Meta description: 148 characters

    Your meta description is 148 characters: “International flower delivery to 123+ countries. Fresh bouquets by local florists with next-day delivery. Flat $14.95 f…”.

  • One H1 headline

    Your main headline reads: “International Flower Delivery to 123+ Countries”.

  • Title: 58 characters

    Your title is a healthy 58 characters: “International Flower Delivery to 123+ Countries | abcFlora”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: FAQPage, OnlineStore and WebSite.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • 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://abcflora.com/sitemap.xml.

AI search readiness

100
4 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.

  • Organization data: 6 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.

  • Text is in the HTML

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

  • llms.txt published

    The site publishes /llms.txt (6 KiB, 39 links), a plain-text guide to the site for AI tools.

Other pages

100
  • 15 internal pages checked

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

7 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 10087
  • 47 small tap targets

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

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to construct 'URL': Invalid URL”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Security and trust

100
  • Short HSTS lifetime

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

  • 1 link through redirect chains

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

  • No Referrer-Policy

    No Referrer-Policy header, so full URLs can leak to the sites you link to.

  • No Permissions-Policy

    No Permissions-Policy header to switch off camera, microphone and location for embedded content.

  • Deprecated X-XSS-Protection

    X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

  • No security.txt

    There is no /.well-known/security.txt telling researchers how to report a security problem to you.

7 checks passed
  • Served over HTTPS

    The homepage is served over HTTPS (abcflora.com).

  • Valid certificate (56 days left)

    The certificate from Let's Encrypt · YE1 verifies for abcflora.com and is valid for another 56 days.

  • Protected from clickjacking

    X-Frame-Options or a frame-ancestors policy stops other sites framing yours.

  • Content-Security-Policy set

    A Content-Security-Policy is set, the main browser-side defence against injected scripts.

  • http:// redirects to https

    http://abcflora.com redirects to the secure version.

  • HTTP/2

    The server speaks HTTP/2, so browsers load many files over one connection.

  • All 47 links work

    All 47 links checked from your homepage (40 internal, 7 external) answered without errors.

Domain and trust

  • DNSSEC is off

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

3 checks passed
  • Domain is 25 years old

    25 years

    abcflora.com was registered in May 2001 through GoDaddy Online Services Cayman Islands Ltd.. An established domain carries more trust with email providers and search engines.

  • Certificate issuers are restricted

    CAA records allow only pki.goog, ssl.com, comodoca.com and digicert.com to issue certificates for abcflora.com, so a mis-issued certificate from anyone else is refused.

  • Registered until May 2027

    abcflora.com is registered until May 2027.

Content and conversion

2 to fix79
  • No call to action on the first screen

    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 direct contact details

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

  • About 766 words of copy

    The homepage carries about 766 words of visible text.

5 checks passed
  • 3 calls to action

    The homepage has 3 calls to action, for example “place an order on our website”, “Contact us” and “Transparent Pricing”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 3 testimonial or review blocks, a star rating and 2 trust badges.

  • Analytics in place

    Analytics detected: Cloudflare Web Analytics.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Email authentication

85
  • Email authentication score: 85/100

    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.

3 checks passed
  • DMARC policy: quarantine

    DMARC tells receivers to quarantine mail that fails authentication.

  • SPF in place (~all)

    An SPF record lists your sending servers and marks other mail as suspicious (~all): “v=spf1 include:zoho.com include:shops.shopify.com include:_spf.klaviyo.com ~all”.

  • DKIM signing found

    A DKIM key is published (selector “zoho”), so receivers can verify mail really came from you.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads 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.

  • 9 cookies set on arrival

    9

    Opening the homepage sets 9 cookies (measured from a US location before any click).

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

  • 15 other companies contacted

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

Upkeep, stack and company

Stack

E-commerce
Shopify
Hosting
Cloudflare

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 19 issues on abcflora.com, including 8 speed issues, 1 SEO issue and 2 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