Website review, no card needed
flowerswaynejones.com website review
Visit site (opens in a new tab)Reviewed 8 November 202643 issues · 81 checks
This review found 43 issues worth fixing on flowerswaynejones.com, 13 of them high impact, across 81 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
68DClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
How it loaded on a phone
0.8 s
1.5 s
2.3 s
3.1 s
3.8 s
4.6 s
5.4 s
6.2 s
Speed
Improve image delivery
2.0 s · 5.8 MB68 images could be 5.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.0 s faster on a phone.
Use efficient cache lifetimes
1.6 s · 5.1 MB110 files are served with short cache lifetimes, so returning visitors download them again (5.1 MB).
Reduce unused JavaScript
1.9 s · 310 KiBAbout 310 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.9 s faster on a phone.
Mobile performance score: 58
58/100Your mobile performance score is 58. Pages that score under 90 lose visitors before the first paint.
Reduce unused CSS
720 ms · 135 KiBAbout 135 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 720 ms faster on a phone.
5 third-party services on the page
5 third-party services load with your homepage (gdvchat.com, Cloudflare and Sentry and others), adding 3.0 MB and 86 ms of main-thread time.
plcl.me adds 0 ms
0 msplcl.me costs a phone 0 ms of main-thread work and 2.5 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.
Main-thread work: 2.4 s
A phone's processor spends 2.4 s on main-thread work while loading, 933 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
2,264 HTML elements
The page has 2,264 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
gdvchat.com adds 80 ms
80 msgdvchat.com costs a phone 80 ms of main-thread work and 541 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.
4 long tasks on the main thread
4 long tasks block the main thread while loading, the longest for 207 ms. During a long task the page ignores taps.
Legacy JavaScript
150 ms · 27 KiBPolyfills for old browsers add 27 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Render-blocking requests
150 ms1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 150 ms.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
1 checks passed
Server response: 14 ms
14 msYour server sent the HTML in 14 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 19.4 s
19.4 sYour largest element takes 19.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “1”.
Time to Interactive: 20.0 s
20.0 sThe page becomes fully interactive after 20.0 s. Good is under 3.8 s.
Speed Index: 10.9 s
10.9 sVisually, the page fills in at 10.9 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.4 s
3.4 sThe first text or image appears after 3.4 s on a phone. Good is under 1.8 s.
3 images without width and height
3 images have no width and height attributes, so the layout jumps as each one loads.
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: 129 ms
129 msScripts block the page for only 129 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 8.9 MB in 191 requests
8.9 MBYour homepage downloads 8.9 MB in 191 requests on a phone: images 7.3 MB (126), scripts 956 KiB (38) and fonts 372 KiB (12). Under 2 MB keeps phones on slow connections fast.
5 images over 500 KB
5 images weigh 3.4 MB together. On a phone connection a single image that size takes seconds.
6 images in older formats
6 images (3.5 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 far larger than shown
366 KiB1 image is downloaded at several times the size a phone draws it, for example dcf42d2a-632c-45f3-b186-da17b5e00ac3.svg at 1,280 px wide, shown at 28 px. Resized copies would save about 366 KiB.
1 image below the first screen load straight away
1 image further down the page (20 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 2.5 g of CO₂ per visit
2.52 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.52 g of CO₂e: 302.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
3 buttons without a name
3 buttons have no accessible name, so screen readers announce just “button”.
36 tap targets too small
36 tap targets are too small or too close together to hit reliably with a finger.
Scrollable region must have keyboard access (2 elements)
Scrollable region must have keyboard access: 2 elements on the page fail this check, rated serious by axe-core.
All page content should be contained by landmarks (109 elements)
All page content should be contained by landmarks: 109 elements on the page fail this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
2 links without text
2 visible links have no text or label, so screen readers cannot say where they go.
2 checks passed
Every image has alt text
All 242 images in the HTML carry an alt attribute.
35 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 42 WCAG 2.2 A/AA and best-practice rules on the phone render: 35 passed and 7 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (83 characters)
Your title is 83 characters, so Google will cut it off around 60: “RAJAMAHJONG - Platform Terbaik Bermain Game Online Resmi Terpercaya Banyak Bonusnya”.
Canonical points to another host
Your canonical URL points to sankalppittsburghmenu.com, not flowerswaynejones.com, so Google may credit that host instead.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
Meta description is long (189 characters)
Your meta description is 189 characters; Google truncates after about 160, so the end of your pitch is cut.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
No XML sitemap
No XML sitemap at https://flowerswaynejones.com/sitemap.xml, so Google discovers your pages only by following links.
No robots.txt
There is no robots.txt at flowerswaynejones.com/robots.txt, the first file search crawlers ask for.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
32 internal links, 7 external
The homepage links to 32 pages on flowerswaynejones.com and 7 external pages.
1 checks passed
One H1 headline
Your main headline reads: “RAJAMAHJONG - Platform Terbaik Bermain Game Online Resmi Terpercaya Banyak Bonusnya”.
AI search readiness
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://flowerswaynejones.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.
1 checks passed
Text is in the HTML
Your server sends the page's text in the HTML (386 words), so crawlers that don't run JavaScript still read it.
Other pages
14 pages share a title
/, https://flowerswaynejones.com/promotion, https://flowerswaynejones.com/hot-games, https://flowerswaynejones.com/games/slot, https://flowerswaynejones.com/games/casino and https://flowerswaynejones.com/games/sport and 8 others all use the title “RAJAMAHJONG - Platform Terbaik Bermain Game Online Resmi Terpercaya B…”. Search engines can't tell which page to show for a search, so each competes with the others.
13 pages share a meta description
https://flowerswaynejones.com/promotion, https://flowerswaynejones.com/hot-games, https://flowerswaynejones.com/games/slot, https://flowerswaynejones.com/games/casino, https://flowerswaynejones.com/games/sport and https://flowerswaynejones.com/games/crash_game and 7 others use the same meta description. A description written for each page earns more clicks.
12 pages without an H1
https://flowerswaynejones.com/promotion, https://flowerswaynejones.com/hot-games, https://flowerswaynejones.com/games/slot, https://flowerswaynejones.com/games/casino, https://flowerswaynejones.com/games/sport and https://flowerswaynejones.com/games/crash_game and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.
11 pages with very little text
https://flowerswaynejones.com/promotion, https://flowerswaynejones.com/games/slot, https://flowerswaynejones.com/games/casino, https://flowerswaynejones.com/games/sport, https://flowerswaynejones.com/games/crash_game and https://flowerswaynejones.com/games/fishing and 5 others have 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.
14 internal pages checked
We fetched 14 pages linked from your homepage and read each the way a search engine does.
5 checks passed
Linked pages load
All 14 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 14 pages that loaded have a meta description.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 14 pages that loaded have a <title>.
Best practices
36 small tap targets
36 of 82 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 429 ()”.
5 distorted images
5 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
Missing source maps
Large scripts ship without source maps.
6 low-resolution images
6 images are served at too low a resolution for sharp phone screens.
Browser-reported issues
Chrome logged issues while loading the page (“Mixed content”).
Requests the notification permission on page load
Requests the notification permission on page load.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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.
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 364 words of copy
The homepage carries about 364 words of visible text.
3 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “📲 APK MOBILE Download App”.
1 call to action
The homepage has 1 call to action, for example “Download Aplikasi”.
2 short forms
2 short forms (0 fields at most) are right on the homepage.
Privacy and tracking
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.
5 other companies contacted
Loading the homepage contacts 5 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 flowerswaynejones.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Go beyond the website
What your $25 Growth Playbook adds
This review found 43 issues on flowerswaynejones.com, including 15 speed issues, 7 SEO issues and 3 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.