Website review, no card needed
5700flowers.com website review
Visit site (opens in a new tab)Reviewed 22 November 202644 issues · 78 checks
This review found 44 issues worth fixing on 5700flowers.com, 20 of them high impact, across 78 checks. The most urgent: use efficient cache lifetimes. 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
64DClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
How it loaded on a phone
1.1 s
2.1 s
3.2 s
4.2 s
5.3 s
6.4 s
7.4 s
8.5 s
Speed
Use efficient cache lifetimes
3.9 s · 1.9 MB32 files are served with short cache lifetimes, so returning visitors download them again (1.9 MB).
Improve image delivery
2.3 s · 986 KiB9 images could be 986 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.3 s faster on a phone.
Document request latency
2.0 s · 29 KiBThe HTML itself could arrive about 2.0 s sooner: redirects, a slow server response or missing compression delay everything after it.
Render-blocking requests
1.5 s18 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.5 s.
Mobile performance score: 63
63/100Your mobile performance score is 63. Pages that score under 90 lose visitors before the first paint.
Avoid multiple page redirects
870 msThe page goes through 3 redirects before it starts loading, costing about 870 ms. Link and advertise the final URL directly.
Reduce unused JavaScript
380 ms · 178 KiBAbout 178 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 380 ms faster on a phone.
4 third-party services on the page
4 third-party services load with your homepage (Facebook, getbutton.io and FontAwesome CDN and others), adding 665 KiB and 368 ms of main-thread time.
Reduce unused CSS
190 ms · 22 KiBAbout 22 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 190 ms faster on a phone.
Minify JavaScript
190 ms · 7 KiB7 KiB could be saved by minifying JavaScript.
Minify CSS
190 ms · 5 KiB5 KiB could be saved by minifying CSS.
Legacy JavaScript
150 ms · 11 KiBPolyfills for old browsers add 11 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
4 long tasks on the main thread
4 long tasks block the main thread while loading, the longest for 141 ms. During a long task the page ignores taps.
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.
2 checks passed
Main-thread work: 1.0 s
A phone's processor spends 1.0 s on main-thread work while loading, 452 ms of it running JavaScript. That is comfortably low.
Server response: 213 ms
213 msYour server sent the HTML in 213 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 7.5 s
7.5 sYour largest element takes 7.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Malaysia Local flower shop in Desa Petaling, provide fast s…”. Most of its time is element render delay (5.3 s).
Speed Index: 9.9 s
9.9 sVisually, the page fills in at 9.9 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 7.5 s
7.5 sThe page becomes fully interactive after 7.5 s. Good is under 3.8 s.
19 images without width and height
19 images have no width and height attributes, so the layout jumps as each one loads.
First Contentful Paint: 2.1 s
2.1 sThe first text or image appears after 2.1 s on a phone. Good is under 1.8 s.
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.
2 checks passed
Total Blocking Time: 153 ms
153 msScripts block the page for only 153 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0.016
0.016The layout barely moves while loading (CLS 0.016, good is under 0.1).
Images and page weight
Page weight: 2.2 MB in 44 requests
2.2 MBYour homepage downloads 2.2 MB in 44 requests on a phone: images 1.4 MB (11), scripts 701 KiB (13) and stylesheets 51 KiB (12). Under 2 MB keeps phones on slow connections fast.
5 images in older formats
5 images (675 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.
About 0.6 g of CO₂ per visit
0.64 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.64 g of CO₂e: 76.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
19 text elements with low contrast
19 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
5 tap targets too small
5 tap targets are too small or too close together to hit reliably with a finger.
Elements must only use permitted ARIA attributes (1 element)
Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.
<html> element must have a lang attribute (1 element)
<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.
<marquee> elements are deprecated and must not be used (1 element)
<marquee> elements are deprecated and must not be used: 1 element on the page fails this check, rated serious by axe-core.
59 images without alt text
59 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (28 elements)
All page content should be contained by landmarks: 28 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
3 form fields without a label
3 form fields have no label, so screen readers announce an empty box and autofill guesses.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
No page language
The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.
1 checks passed
26 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 37 WCAG 2.2 A/AA and best-practice rules on the phone render: 26 passed and 11 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
robots.txt blocks all crawlers
Your robots.txt disallows the whole site for every crawler, so search engines are told to stay out.
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
46 links crawlers can't follow
46 links have no real href, so search engines can't follow them.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
Meta description is long (281 characters)
Your meta description is 281 characters; Google truncates after about 160, so the end of your pitch is cut.
No social preview image
No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
108 internal links, 12 external
The homepage links to 108 pages on 5700flowers.com and 12 external pages.
2 checks passed
Title: 55 characters
Your title is a healthy 55 characters: “5700Flowers.com - Same Day Fast Flower Delivery in KL -”.
XML sitemap found
Your XML sitemap is reachable at https://5700flowers.com/sitemap.xml.
AI search readiness
robots.txt blocks 6 AI answer engine crawlers
6 of 6Your robots.txt shuts out ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Claude search (Claude-SearchBot), Claude (Claude-User), Perplexity (PerplexityBot) and Perplexity (Perplexity-User). These fetch pages to answer people's questions and cite the source, so your site can't be quoted or linked in those answers.
No Organization structured data
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.
No llms.txt
There is no https://5700flowers.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.
Opted out of AI training for 5 crawlers
robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers.
1 checks passed
Text is in the HTML
Your server sends the page's text in the HTML (586 words), so crawlers that don't run JavaScript still read it.
Other pages
3 linked pages are broken
Your homepage links to https://5700flowers.com/show-category.asp, https://5700flowers.com/show-item.asp and https://5700flowers.com/show-help.asp, which answer with an error. Visitors hit a dead end and search engines drop them.
7 internal pages checked
We fetched 7 pages linked from your homepage and read each the way a search engine does.
Best practices
No mobile viewport
No viewport meta tag, so phones render the desktop layout zoomed out.
Scrolls sideways on phones
On a 390 px-wide phone the page scrolls sideways, a sign that something is wider than the screen.
5 small tap targets
5 of 9 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 JavaScript error while loading
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 ()”.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
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 social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
Phone number is not tap-to-call
Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.
No risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
About 419 words of copy
The homepage carries about 419 words of visible text.
3 checks passed
4 calls to action
The homepage has 4 calls to action, for example “Sign Up As New Member”, “Member Sign Up” and “Submit Order Details”.
2 short forms
2 short forms (2 fields at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Meta Pixel.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads Meta Pixel (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.
4 cookies set on arrival
4Opening the homepage sets 4 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.
6 other companies contacted
Loading the homepage contacts 6 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 5700flowers.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Hosting
- GB Network Solutions Sdn. Bhd.
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 44 issues on 5700flowers.com, including 12 speed issues, 7 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.