Website review, no card needed
gratitudepoem.com website review
Visit site (opens in a new tab)Reviewed 17 November 202641 issues · 76 checks
This review found 41 issues worth fixing on gratitudepoem.com, 18 of them high impact, across 76 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
62DClosest 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.2 s
2.4 s
3.6 s
4.8 s
6.0 s
7.2 s
8.4 s
9.6 s
Speed
Improve image delivery
33.8 s · 6.2 MB21 images could be 6.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 33.8 s faster on a phone.
Avoid multiple page redirects
2.2 sThe page goes through 2 redirects before it starts loading, costing about 2.2 s. Link and advertise the final URL directly.
Render-blocking requests
1.7 s14 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.7 s.
Mobile performance score: 60
60/100Your mobile performance score is 60. Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
600 ms · 74 KiBAbout 74 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 600 ms faster on a phone.
e8rongyaokeji.com adds 40 ms
40 mse8rongyaokeji.com costs a phone 40 ms of main-thread work and 830 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.
5 third-party services on the page
5 third-party services load with your homepage (51.la, e8rongyaokeji.com and Baidu Analytics and others), adding 915 KiB and 129 ms of main-thread time.
Use efficient cache lifetimes
22 KiB7 files are served with short cache lifetimes, so returning visitors download them again (22 KiB).
Legacy JavaScript
11 KiBPolyfills for old browsers add 11 KiB JavaScript that modern phones do not need.
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.
Minify JavaScript
3 KiB3 KiB could be saved by minifying JavaScript.
Minify CSS
2 KiB2 KiB could be saved by minifying CSS.
2 checks passed
Main-thread work: 1.1 s
A phone's processor spends 1.1 s on main-thread work while loading, 343 ms of it running JavaScript. That is comfortably low.
Server response: 2 ms
2 msYour server sent the HTML in 2 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 67.5 s
67.5 sYour largest element takes 67.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Time to Interactive: 67.9 s
67.9 sThe page becomes fully interactive after 67.9 s. Good is under 3.8 s.
Speed Index: 9.2 s
9.2 sVisually, the page fills in at 9.2 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.
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
Cumulative Layout Shift: 0.007
0.007The layout barely moves while loading (CLS 0.007, good is under 0.1).
Total Blocking Time: 0 ms
0 msScripts block the page for only 0 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 12.6 MB in 176 requests
12.6 MBYour homepage downloads 12.6 MB in 176 requests on a phone: images 12.3 MB (99), scripts 303 KiB (50) and HTML 29 KiB (4). Under 2 MB keeps phones on slow connections fast.
12 images far larger than shown
2.5 MB12 images are downloaded at several times the size a phone draws them, for example 61D6DF161E9BD86E0548006D682_928CAED1_10CAFA.png at 2,048 px wide, shown at 178 px. Resized copies would save about 2.5 MB.
1 image over 500 KB
61D6DF161E9BD86E0548006D682_928CAED1_10CAFA.png weighs 1.0 MB. On a phone connection a single image that size takes seconds.
22 images in older formats
22 images (5.2 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.
About 3.6 g of CO₂ per visit
3.58 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.58 g of CO₂e: 430.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
<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.
Links must have discernible text (1 element)
Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.
16 images without alt text
16 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (39 elements)
All page content should be contained by landmarks: 39 elements on the page fail this check, rated moderate by axe-core.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
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
18 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 24 WCAG 2.2 A/AA and best-practice rules on the phone render: 18 passed and 6 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
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.
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 XML sitemap
No XML sitemap at https://www.gratitudepoem.com/sitemap.xml, so Google discovers your pages only by following links.
No robots.txt
There is no robots.txt at gratitudepoem.com/robots.txt, the first file search crawlers ask for.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
66 internal links, 0 external
The homepage links to 66 pages on gratitudepoem.com and 0 external pages.
3 checks passed
Meta description: 105 characters
Your meta description is 105 characters: “7️⃣「马到成功」让你玩的同时心情得到一个放松,WilliamHill中文官方网站致力于打造垂直整合的“平台+内容+终端+应用”的生态模式,william威廉中文官网拥有更快乐休闲方式,始终保持业界的领先地位。”.
One H1 headline
Your main headline reads: “威廉希尔(WilliamHill-中文官方网站)-Official Website”.
Title: 41 characters
Your title is a healthy 41 characters: “威廉希尔(WilliamHill-中文官方网站)-Official Website”.
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.
Other pages
16 pages share a title
/, https://www.gratitudepoem.com/xygk/xyjj.html, https://www.gratitudepoem.com/xygk/yzjy.html, https://www.gratitudepoem.com/xygk/jgsz.html, https://www.gratitudepoem.com/xygk/ldjs.html and https://www.gratitudepoem.com/xygk/xkjj.html and 10 others all use the title “威廉希尔(WilliamHill-中文官方网站)-Official Website”. Search engines can't tell which page to show for a search, so each competes with the others.
15 pages share a meta description
https://www.gratitudepoem.com/xygk/xyjj.html, https://www.gratitudepoem.com/xygk/yzjy.html, https://www.gratitudepoem.com/xygk/jgsz.html, https://www.gratitudepoem.com/xygk/ldjs.html, https://www.gratitudepoem.com/xygk/xkjj.html and https://www.gratitudepoem.com/szdw.html and 9 others use the same meta description. A description written for each page earns more clicks.
15 pages with very little text
https://www.gratitudepoem.com/xygk/xyjj.html, https://www.gratitudepoem.com/xygk/yzjy.html, https://www.gratitudepoem.com/xygk/jgsz.html, https://www.gratitudepoem.com/xygk/ldjs.html, https://www.gratitudepoem.com/xygk/xkjj.html and https://www.gratitudepoem.com/szdw.html and 9 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.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 58 found) and read each the way a search engine does.
6 checks passed
Linked pages load
All 15 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 15 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 15 pages that loaded have a <title>.
Best practices
No mobile viewport
No viewport meta tag, so phones render the desktop layout zoomed out.
18 small tap targets
18 of 44 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.”).
30 distorted images
30 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
1 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
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 calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
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.
Only about 26 words
The homepage has only about 26 words of visible text; thin pages give Google and first-time buyers little to go on.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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.
Privacy and tracking
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.
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.
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 gratitudepoem.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- jQuery
- Hosting
- Peg La Peg Tech Inc
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 41 issues on gratitudepoem.com, including 10 speed issues, 6 SEO issues and 6 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.