budsnbows.com website review

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

16 images could be 283 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.

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

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

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

Shopify costs a phone 28 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.

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

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

2 long tasks block the main thread while loading, the longest for 79 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.

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

4 KiB could be saved by minifying JavaScript.

Your largest element takes 6.1 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 6.2 s. Good is under 3.8 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.

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

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

118 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 on the page fails this check, rated moderate by axe-core.

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

Your title is 67 characters, so Google will cut it off around 60: “North Little Rock Florist | Same Day Flower Delivery by Buds N Bows”.

Structured data found (FAQPage, LocalBusiness, Organization and WebSite) but with 3 problems, for example “LocalBusiness: logo is not an absolute URL ("//budsnbows.com/cdn/shop/files/03-1237AA_Buds_N_Bows.p…”.

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

The homepage links to 528 pages on budsnbows.com and 1 external page.

There is no /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.

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

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

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

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

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

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

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

budsnbows.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

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

Social proof on the homepage: 1 testimonial or review block. 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 phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

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

budsnbows.com has no DMARC record, so nothing tells receivers what to do with mail that fails SPF or DKIM. Gmail and Yahoo require DMARC from bulk senders.

budsnbows.com has no SPF record, so mail servers can't tell which servers may send email as you. Your mail lands in spam more often, and anyone can send mail pretending to be you.

We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

budsnbows.com has no MX record, so it receives no email. SPF -all and DMARC reject still matter: they stop others sending mail as you.

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.

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.

Opening the homepage sets 5 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 5 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.