zingplants.com website review

The page goes through 3 redirects before it starts loading, costing about 3.9 s. Link and advertise the final URL directly.

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

8 third-party services load with your homepage (Google Tag Manager, arenaflowers.com and Bing Ads and others), adding 1.4 MB and 778 ms of main-thread time.

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

Google Tag Manager costs a phone 511 ms of main-thread work and 389 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.

1 image could be 442 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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

arenaflowers.com costs a phone 133 ms of main-thread work and 900 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.

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

About 154 KiB of JavaScript is downloaded but never used on this page.

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

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.

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

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

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

Your largest element takes 3.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Zing Flowers has moved to our long term friends and partner…”. Most of its time is element render delay (2.7 s).

Scripts block taps and scrolling for 222 ms in total while the page loads. Good is under 200 ms.

Your homepage downloads 2.4 MB in 120 requests on a phone: images 1.1 MB (23), scripts 947 KiB (62) and other files 237 KiB (23). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example YOURWORLDOURMISSION_BANNERIMAGE_ce72881182_074971ee75.jpg at 3,360 px wide, shown at 326 px. Resized copies would save about 429 KiB.

3 images (581 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.

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

4 elements use ARIA attributes their role does not allow, which confuses screen readers.

1 button has no accessible name, so screen readers announce just “button”.

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

Some lists contain elements other than list items, which screen readers announce wrongly.

1 tap target is too small or too close together to hit reliably with a finger.

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

The skip-link target should exist and be focusable: 1 element on the page fails this check, rated moderate by axe-core.

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

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

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

Your canonical URL points to zingflowers.com, not zingplants.com, so Google may credit that host instead.

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

There are 2 <h1> headlines (“” and “Zing Flowers has moved”). One clear main headline is easier for people and search engines.

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

3 links have no real href, so search engines can't follow them.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 35 pages on zingplants.com and 15 external pages.

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.

Your homepage links to https://zingplants.com/collections/fairtrade, which answers with an error. Visitors hit a dead end and search engines drop it.

https://zingplants.com/pages/about-us is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://zingplants.com/collections/bouquets, https://zingplants.com/collections/letterbox, https://zingplants.com/collections/gifts, https://zingplants.com/collections/plants, https://zingplants.com/pages/subscriptions and https://zingplants.com/pages/contact-us and 1 other all use the title “Zing Flowers has moved to Arena Flowers”. Search engines can't tell which page to show for a search, so each competes with the others.

https://zingplants.com/collections/bouquets, https://zingplants.com/collections/letterbox, https://zingplants.com/collections/gifts, https://zingplants.com/collections/plants, https://zingplants.com/pages/subscriptions and https://zingplants.com/pages/contact-us and 1 other use the same meta description. A description written for each page earns more clicks.

https://zingplants.com/pages/flower-delivery has no <h1> headline, so visitors and search engines get no clear main topic.

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

2 images failed to load on a phone, for example https://bat.bing.net/action/0?ti=5140988&tm=gtm002&Ver=2&mid=a9b426fe-6200-4d6d-b9dc-cf0754426674&bo=3&pi=918639831&lg=en-US&sw=390&sh=844&sc=24&nwd=1&tl=Zing%20Flowers%20has%20moved%20to%20Arena%20Fl.

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

Chrome logged issues while loading the page (“Content security policy”).

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

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

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

The homepage shows no opening hours. If customers visit or call, show when.

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

The homepage carries about 393 words of visible text.

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