Website review, no card needed
gardenflowersllc.com website review
Visit site (opens in a new tab)Reviewed 8 November 202657 issues · 93 checks
This review found 57 issues worth fixing on gardenflowersllc.com, 24 of them high impact, across 93 checks. The most urgent: improve image delivery. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
59F- #123,310 of 126,150 reviewed websitesbeats 2%
- #69,867 of 70,373 online storesbeats 1%
- #63,556 of 63,900 Shopify storesbeats 0%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Jul 25, 2026 | 2.7 s |
| Aug 1, 2026 | 2.6 s |
| Aug 8, 2026 | 2.6 s |
| Aug 15, 2026 | 2.6 s |
| Aug 22, 2026 | 2.5 s |
| Aug 29, 2026 | 2.5 s |
| Sep 5, 2026 | 2.5 s |
| Sep 12, 2026 | 2.5 s |
| Sep 19, 2026 | 2.6 s |
| Sep 26, 2026 | 3.5 s |
| Oct 3, 2026 | 3.6 s |
| Oct 10, 2026 | 3.7 s |
| Oct 17, 2026 | 3.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Jul 25, 2026 | 535 ms |
| Aug 1, 2026 | 530 ms |
| Aug 8, 2026 | 538 ms |
| Aug 15, 2026 | 547 ms |
| Aug 22, 2026 | 539 ms |
| Aug 29, 2026 | 540 ms |
| Sep 5, 2026 | 556 ms |
| Sep 12, 2026 | 569 ms |
| Sep 19, 2026 | 680 ms |
| Sep 26, 2026 | 5.5 s |
| Oct 3, 2026 | 4.3 s |
| Oct 10, 2026 | 3.1 s |
| Oct 17, 2026 | 2.6 s |
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
How it loaded on a phone
1.1 s
2.3 s
3.4 s
4.5 s
5.7 s
6.8 s
7.9 s
9.1 s
Speed
Improve image delivery
22.7 s · 4.4 MB2 images could be 4.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 22.7 s faster on a phone.
Use efficient cache lifetimes
9.9 s · 3.0 MB55 files are served with short cache lifetimes, so returning visitors download them again (3.0 MB).
Reduce unused JavaScript
4.1 s · 1.3 MBAbout 1.3 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.1 s faster on a phone.
Render-blocking requests
2.5 s14 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.5 s.
Mobile performance score: 34
34/100Your mobile performance score is 34. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
4,661 HTML elements
The page has 4,661 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Main-thread work: 4.6 s
A phone's processor spends 4.6 s on main-thread work while loading, 2.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (Adobe Tag Manager, sprinklr.com and Google Tag Manager and others), adding 2.1 MB and 1.4 s of main-thread time.
Adobe Tag Manager adds 276 ms
276 msAdobe Tag Manager costs a phone 276 ms of main-thread work and 155 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.
sprinklr.com adds 235 ms
235 mssprinklr.com costs a phone 235 ms of main-thread work and 436 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.
Google Maps adds 140 ms
140 msGoogle Maps costs a phone 140 ms of main-thread work and 471 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.
Google CDN adds 113 ms
113 msGoogle CDN costs a phone 113 ms of main-thread work and 353 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.
14 long tasks on the main thread
14 long tasks block the main thread while loading, the longest for 243 ms. During a long task the page ignores taps.
Legacy JavaScript
30 KiBPolyfills for old browsers add 30 KiB JavaScript that modern phones do not need.
Minify JavaScript
10 KiB10 KiB could be saved by minifying JavaScript.
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.
1 checks passed
Server response: 468 ms
468 msYour server sent the HTML in 468 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 32.8 s
32.8 sYour largest element takes 32.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Popup Banner”.
Time to Interactive: 32.8 s
32.8 sThe page becomes fully interactive after 32.8 s. Good is under 3.8 s.
Speed Index: 10.6 s
10.6 sVisually, the page fills in at 10.6 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.2 s
3.2 sThe first text or image appears after 3.2 s on a phone. Good is under 1.8 s.
Tap response (INP) got 433% slower for real visitors
+433%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 535 ms to 2.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 38% slower for real visitors
+38%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.7 s to 3.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
100 images without width and height
100 images have no width and height attributes, so the layout jumps as each one loads.
Cumulative Layout Shift: 0.242
0.242The layout shifts by 0.242 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Total Blocking Time: 548 ms
548 msScripts block taps and scrolling for 548 ms in total while the page loads. Good is under 200 ms.
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.
Images and page weight
Page weight: 7.5 MB in 179 requests
7.5 MBYour homepage downloads 7.5 MB in 179 requests on a phone: images 4.9 MB (16), scripts 2.4 MB (106) and HTML 136 KiB (8). Under 2 MB keeps phones on slow connections fast.
2 images over 500 KB
2 images weigh 4.7 MB together. On a phone connection a single image that size takes seconds.
1 image far larger than shown
1.8 MB1 image is downloaded at several times the size a phone draws it, for example logo.webp at 1,920 px wide, shown at 200 px. Resized copies would save about 1.8 MB.
1 image in older formats
1 image (2.7 MB) is 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 below the first screen load straight away
1 image further down the page (2.7 MB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 2.1 g of CO₂ per visit
2.12 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.12 g of CO₂e: 254.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
4 buttons without a name
4 buttons have no accessible name, so screen readers announce just “button”.
Invalid ARIA attributes
1 element use ARIA attributes their role does not allow, which confuses screen readers.
Certain ARIA roles must contain particular children (1 element)
Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.
ARIA attributes must conform to valid values (1 element)
ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.
98 tap targets too small
98 tap targets are too small or too close together to hit reliably with a finger.
ARIA dialog and alertdialog nodes should have an accessible name (32 elements)
ARIA dialog and alertdialog nodes should have an accessible name: 32 elements on the page fail this check, rated serious by axe-core.
4 text elements with low contrast
4 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 (131 elements)
All page content should be contained by landmarks: 131 elements on the page fail this check, rated moderate by axe-core.
5 form fields without a label
5 form fields have no label, so screen readers announce an empty box and autofill guesses.
Elements use prohibited ARIA attributes
Elements use prohibited ARIA attributes (1 element).
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
Headings should not be empty (1 element)
Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (24 elements).
2 checks passed
Every image has alt text
All 129 images in the HTML carry an alt attribute.
52 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 62 WCAG 2.2 A/AA and best-practice rules on the phone render: 52 passed and 10 failed. 7 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (80 characters)
Your title is 80 characters, so Google will cut it off around 60: “TAWONBET: Link Situs Online No 1 Terbaik Didunia Kualitas Rtp Tertinggi Saat Ini”.
2 H1 headlines
There are 2 <h1> headlines (“TAWONBET : Link Situs Online No 1 Terbaik Didunia…” and “TAWONBET: Link Situs Online No 1 Terbaik Didunia …”). One clear main headline is easier for people and search engines.
25 links crawlers can't follow
25 links have no real href, so search engines can't follow them.
Meta description is long (163 characters)
Your meta description is 163 characters; Google truncates after about 160, so the end of your pitch is cut.
No XML sitemap
No XML sitemap at https://new-tawonbet.com/sitemap.xml, so Google discovers your pages only by following links.
72 internal links, 60 external
The homepage links to 72 pages on gardenflowersllc.com and 60 external pages.
4 checks passed
Canonical URL set
The canonical URL is https://new-tawonbet.com/.
Structured data in place
Structured data found: BreadcrumbList, FAQPage, OfferCatalog, Organization and Product.
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.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
No llms.txt
There is no https://new-tawonbet.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.
2 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.
Text is in the HTML
Your server sends the page's text in the HTML (3,436 words), so crawlers that don't run JavaScript still read it.
Other pages
3 pages point its canonical at the homepage
https://new-tawonbet.com/kebijakan-privasi, https://new-tawonbet.com/legal and https://new-tawonbet.com/sitemap declare the homepage as their canonical URL, which tells Google they are copies of the homepage and keeps them out of search results. A site-wide template setting usually causes this.
4 pages share a title
/, https://new-tawonbet.com/kebijakan-privasi, https://new-tawonbet.com/legal and https://new-tawonbet.com/sitemap all use the title “TAWONBET: Link Situs Online No 1 Terbaik Didunia Kualitas Rtp Terting…”. Search engines can't tell which page to show for a search, so each competes with the others.
3 pages share a meta description
https://new-tawonbet.com/kebijakan-privasi, https://new-tawonbet.com/legal and https://new-tawonbet.com/sitemap use the same meta description. A description written for each page earns more clicks.
3 pages slow to respond
https://new-tawonbet.com/kebijakan-privasi, https://new-tawonbet.com/legal and https://new-tawonbet.com/sitemap took over 3 s to send their HTML from our server.
3 internal pages checked
We fetched 3 pages linked from your homepage and read each the way a search engine does.
5 checks passed
Linked pages load
All 3 pages we checked loaded without an error.
Every page has a meta description
All 3 pages that loaded have a meta description.
Every page has an H1
Each page we checked has a main headline.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 3 pages that loaded have a <title>.
Best practices
1 broken image
1 image failed to load on a phone, for example https://new-tawonbet.com/#.
45 small tap targets
45 of 60 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Scrolls sideways on phones
On a 390 px-wide phone the page scrolls sideways, a sign that something is wider than the screen.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
1 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “Uncaught ReferenceError: google is not defined”.
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.
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.
About 2,727 words of copy
The homepage carries about 2,727 words of visible text.
5 checks passed
2 calls to action
The homepage has 2 calls to action, for example “TAWONBET Explore Shop” and “Shop”.
9 short forms
9 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 70 testimonial or review blocks and a star rating.
Analytics in place
Analytics detected: Google Analytics and Cloudflare Web Analytics.
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
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Pinterest Tag (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.
14 cookies set on arrival
14Opening the homepage sets 14 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.
27 other companies contacted
Loading the homepage contacts 27 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 gardenflowersllc.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- E-commerce
- Shopify;Shopify Plus
- Analytics
- Google Analytics
- Hosting
- Cloudflare
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 57 issues on gardenflowersllc.com, including 21 speed issues, 5 SEO issues and 2 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.