lunsfordsflowers.com website review

3 images could be 1.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 8.6 s faster on a phone.

14 files are served with short cache lifetimes, so returning visitors download them again (1.4 MB).

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

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

6 third-party services load with your homepage (teepublic.com, Google Analytics and datadoghq-browser-agent.com and others), adding 2.2 MB and 245 ms of main-thread time.

kilat.digital costs a phone 0 ms of main-thread work and 1.8 MB 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.

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

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

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

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.

3 KiB could be saved by minifying JavaScript.

2 KiB could be saved by minifying CSS.

Your largest element takes 13.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Popup Banner”.

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

The layout shifts by 0.231 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

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

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

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.

661c0b574a90b2ec89d39bd2f8a26d92.png weighs 1.8 MB. On a phone connection a single image that size takes seconds.

Your homepage downloads 2.3 MB in 23 requests on a phone: images 1.9 MB (5), scripts 305 KiB (10) and HTML 69 KiB (1). Under 2 MB keeps phones on slow connections fast.

2 images (1.9 MB) 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.

1 image is downloaded at several times the size a phone draws it, for example logo_coloksgp_2_2.png at 1,232 px wide, shown at 150 px. Resized copies would save about 56 KiB.

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

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

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

<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

1 element has a tabindex above 0, which scrambles the keyboard order.

14 images have no alt text, which hurts accessibility and image search.

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

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

7 tap targets are too small or too close together to hit reliably with a finger.

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

The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

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

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

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is 76 characters, so Google will cut it off around 60: “COLOKSGP 𝗓ᶻ Rumah Situs Togel Online Modern & Bandar Toto Macau Tersturktur”.

There are 2 <h1> headlines (“COLOKSGP 𝗓ᶻ Rumah Situs Togel Online Modern & Ba…” and “COLOKSGP 𝗓ᶻ Rumah Situs Togel Online Modern & Ba…”). One clear main headline is easier for people and search engines.

Structured data found ((untyped), BreadcrumbList, FAQPage and Organization) but with 3 problems, for example “Product: no offers (price) block”.

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

The homepage links to 105 pages on lunsfordsflowers.com and 4 external pages.

There is no https://georgiamountainendo.com/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.

Your homepage links to https://georgiamountainendo.com/t-shirts, https://georgiamountainendo.com/intellectual-property-policy, https://georgiamountainendo.com/ccpa, https://georgiamountainendo.com/privacy_policy, https://georgiamountainendo.com/terms and https://georgiamountainendo.com/about and 8 others, which answer with an error. Visitors hit a dead end and search engines drop them.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://georgiamountainendo.com/forms, whose canonical is https://georgiamountainendo.com/our-staff. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://georgiamountainendo.com/forms has no <h1> headline, so visitors and search engines get no clear main topic.

https://georgiamountainendo.com/forms has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

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

5 errors were logged to the browser console while the page loaded, for example “Uncaught TypeError: Cannot set properties of null (setting 'innerHTML')”.

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

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

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

Before a visitor clicks anything, the page loads Google Analytics (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 4 cookies, 1 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 6 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.