flowerchimp.com.ph website review

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

28 images could be 1.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 900 ms faster on a phone.

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

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

About 48 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.

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

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

4 third-party services load with your homepage (Shopify, Google Fonts and Google CDN and others), adding 348 KiB and 1 ms of main-thread time.

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.

1 file is served with short cache lifetimes, so returning visitors download them again (3 KiB).

Your largest element takes 7.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “//www.flowerchimp.com.ph/cdn/shopifycloud/storefront/assets…”.

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

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

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

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

10 images are downloaded at several times the size a phone draws them, for example FC-HP-Fruit-Basket-v1.webp at 1,280 px wide, shown at 365 px. Resized copies would save about 698 KiB.

Your homepage downloads 2.3 MB in 100 requests on a phone: images 1.6 MB (65), fonts 351 KiB (8) and scripts 238 KiB (17). Under 2 MB keeps phones on slow connections fast.

FCHP-banner-mobile-1.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).

3 images (329 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.66 g of CO₂e: 79.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

2 dropdowns have no label.

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

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

Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.

Some list items are not inside a list.

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

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

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

1 visible link has no text or label, so screen readers cannot say where it goes.

Elements with visible text labels do not have matching accessible names. (4 elements).

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

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

The homepage links to 316 pages on flowerchimp.com.ph and 12 external pages.

Your Organization JSON-LD is missing url, logo, sameAs (social profiles) and description. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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

The homepage carries about 1,445 words of visible text.

The page uses urgency cues (a countdown or limited-time wording).

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