Programmable

Website review, no card needed

christellsflowers.com logo

christellsflowers.com website review

Visit site (opens in a new tab)Reviewed 11 November 202621 issues · 70 checks

This review found 21 issues worth fixing on christellsflowers.com, 2 of them high impact, across 70 checks. The most urgent: 105 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

Site score

89B

Closest competitors among Shopify stores

Compare side by side
Real-visitor load time (LCP)75th percentile, phones
1.4 s787 msJun 27Oct 241.2 s
Show as table
DateReal-visitor load time (LCP)
Jun 27, 2026914 ms
Jul 11, 2026881 ms
Jul 18, 2026858 ms
Aug 22, 20261.2 s
Aug 29, 20261.3 s
Oct 17, 20261.2 s
Oct 24, 20261.2 s
Real-visitor tap response (INP)75th percentile, phones
89 ms60 msJul 18Oct 2485 ms
Show as table
DateReal-visitor tap response (INP)
Jul 18, 202663 ms
Aug 22, 202679 ms
Aug 29, 202686 ms
Oct 17, 202685 ms
Oct 24, 202685 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

christellsflowers.com (opens in a new tab)
Full-page screenshot of christellsflowers.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. christellsflowers.com at 0.7 s0.7 s
  2. christellsflowers.com at 1.3 s1.3 s
  3. christellsflowers.com at 2.0 s2.0 s
  4. christellsflowers.com at 2.6 s2.6 s
  5. christellsflowers.com at 3.3 s3.3 s
  6. christellsflowers.com at 4.0 s4.0 s
  7. christellsflowers.com at 4.6 s4.6 s
  8. christellsflowers.com at 5.3 s5.3 s

Speed

5 to fix83

  • Mobile performance score: 83

    83/100

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

  • Improve image delivery

    450 ms · 378 KiB

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

  • Use efficient cache lifetimes

    600 ms · 98 KiB

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

  • Render-blocking requests

    450 ms

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

  • 1,898 HTML elements

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

  • Reduce unused JavaScript

    150 ms · 63 KiB

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

  • 3 third-party services on the page

    3 third-party services load with your homepage (FullStory, Shopify and mercuryhq.com), adding 181 KiB and 167 ms of main-thread time.

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

    4 KiB

    4 KiB could be saved by minifying JavaScript.

2 checks passed

  • Main-thread work: 1.3 s

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

  • Server response: 15 ms

    15 ms

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

Core Web Vitals

5 to fix80

  • Largest Contentful Paint: 4.4 s

    4.4 s

    Your largest element takes 4.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “homepageBannerMetadata_Image_1788292858417.jpeg”.

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

    +20%

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

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

    +36%

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

  • Time to Interactive: 4.4 s

    4.4 s

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

  • Speed Index: 3.6 s

    3.6 s

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

  • Not enough real-visitor data yet

    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.

3 checks passed

  • First Contentful Paint: 1.4 s

    1.4 s

    The first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0.003

    0.003

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

  • Total Blocking Time: 0 ms

    0 ms

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

Images and page weight

2 to fix81

  • Page weight: 2.2 MB in 200 requests

    2.2 MB

    Your homepage downloads 2.2 MB in 200 requests on a phone: images 928 KiB (21), other files 736 KiB (88) and scripts 360 KiB (53). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    homepageBannerMetadata_Image_1744147821312.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).

  • About 0.6 g of CO₂ per visit

    0.62 g

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

2 checks passed

  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

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

Accessibility

3 to fixGoogle 9796

  • 105 text elements with low contrast

    105 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 (1 element)

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

  • 2 form fields without a label

    2 form fields have no label, so screen readers announce an empty box and autofill guesses.

2 checks passed

  • Every image has alt text

    All 21 images in the HTML carry an alt attribute.

  • 51 automated accessibility rules passed

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

SEO

1 to fixGoogle 10096

  • Structured data has 1 problem

    Structured data found (LocalBusiness, Organization and WebSite) but with 1 problem, for example “LocalBusiness: logo is not an absolute URL ("//christellsflowers.com/cdn/shop/files/49-4211AA-Logo_…”.

  • 497 internal links, 7 external

    The homepage links to 497 pages on christellsflowers.com and 7 external pages.

7 checks passed

  • Meta description: 130 characters

    Your meta description is 130 characters: “Florist near me for fresh flowers! Shop Christell's Flowers online for same day delivery in Killeen, TX. Birthday, wedd…”.

  • One H1 headline

    Your main headline reads: “Get Same-Day Flower Delivery in Killeen, TX”.

  • Title: 65 characters

    Your title is a healthy 65 characters: “Killeen Florist | Same Day Flower Delivery by Christell's Flowers”.

  • Canonical URL set

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

  • 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://christellsflowers.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 (2,737 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://christellsflowers.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

1 to fix95

  • 8 pages without an H1

    https://christellsflowers.com/collections/autumn-fall_2022, https://christellsflowers.com/collections/all_occasion_arrangements, https://christellsflowers.com/collections/birthday_bouquets, https://christellsflowers.com/collections/romance_anniversary, https://christellsflowers.com/collections/luxury_arrangements and https://christellsflowers.com/collections/baby and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

6 checks passed

  • Linked pages load

    12 pages of 15 loaded without an error (the rest turned automated requests away).

  • Canonical URLs point to themselves

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

  • Every page has a meta description

    All 12 pages that loaded have a meta description.

  • 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

Google 96100
3 checks passed

  • No console errors

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

  • Tap targets are thumb-sized

    33 of 40 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix85

  • No phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • 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 map or directions link

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

  • About 2,174 words of copy

    The homepage carries about 2,174 words of visible text.

7 checks passed

  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Quick Shop” and “Shop Birthday Flowers”.

  • 12 calls to action

    The homepage has 12 calls to action, for example “Contact Us”, “Why Shop Local?” and “Quick Shop”.

  • 2 short forms

    2 short forms (1 field at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 1 testimonial or review block and a star rating.

  • Opening hours shown

    Your opening hours are on the homepage.

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

  • Risk reducer mentioned

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

Privacy and tracking

1 to fix

  • 1 tracker load before any consent

    1

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

  • 3 cookies set on arrival

    3

    Opening the homepage sets 3 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.

  • 4 other companies contacted

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

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 christellsflowers.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Apps on your store

Your storefront loads 1 app. It is code from another company running for your shoppers.

Apps your storefront loads

Fullstory

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

E-commerce
Shopify
Analytics
FullStory
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 21 issues on christellsflowers.com, including 10 speed issues, 1 SEO issue 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