Website review, no card needed
sunnylove.com.cn website review
Visit site (opens in a new tab)Reviewed 12 November 202649 issues · 80 checks
This review found 49 issues worth fixing on sunnylove.com.cn, 18 of them high impact, across 80 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
54FClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
How it loaded on a phone
2.0 s
4.0 s
6.0 s
8.0 s
10.0 s
12.0 s
14.0 s
16.0 s
Speed
Use efficient cache lifetimes
5.8 s · 1.5 MB17 files are served with short cache lifetimes, so returning visitors download them again (1.5 MB).
Improve image delivery
4.7 s · 1.2 MB5 images could be 1.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 4.7 s faster on a phone.
Render-blocking requests
4.8 s20 files block the first paint until they finish downloading. Deferring or inlining them could save about 4.8 s.
Document request latency
2.5 sThe HTML itself could arrive about 2.5 s sooner: redirects, a slow server response or missing compression delay everything after it.
Font display
1.9 sWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 1.9 s).
iyong.com adds 1.5 s
1.5 siyong.com costs a phone 1.5 s of main-thread work and 1.5 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Avoid multiple page redirects
1.4 sThe page goes through 2 redirects before it starts loading, costing about 1.4 s. Link and advertise the final URL directly.
Mobile performance score: 28
28/100Your mobile performance score is 28. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
6 third-party services on the page
6 third-party services load with your homepage (iyong.com, j-cc.cn and kenfor.com and others), adding 2.1 MB and 1.8 s of main-thread time.
1 long task on the main thread
1 long task block the main thread while loading, the longest for 1.8 s. During a long task the page ignores taps.
Reduce unused JavaScript
600 ms · 171 KiBAbout 171 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.
Reduce unused CSS
300 ms · 68 KiBAbout 68 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
Minify JavaScript
300 ms · 59 KiB59 KiB could be saved by minifying JavaScript.
j-cc.cn adds 226 ms
226 msj-cc.cn costs a phone 226 ms of main-thread work and 556 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.
Main-thread work: 2.5 s
A phone's processor spends 2.5 s on main-thread work while loading, 2.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Legacy JavaScript
8 KiBPolyfills for old browsers add 8 KiB JavaScript that modern phones do not need.
Minify CSS
7 KiB7 KiB could be saved by minifying CSS.
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: 3 ms
3 msYour server sent the HTML in 3 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 11.8 s
11.8 sYour largest element takes 11.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below. Most of its time is resource load delay (10.0 s).
Speed Index: 19.3 s
19.3 sVisually, the page fills in at 19.3 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 6.3 s
6.3 sThe first text or image appears after 6.3 s on a phone. Good is under 1.8 s.
Total Blocking Time: 1.7 s
1.7 sScripts block taps and scrolling for 1.7 s in total while the page loads. Good is under 200 ms.
Time to Interactive: 11.8 s
11.8 sThe page becomes fully interactive after 11.8 s. Good is under 3.8 s.
6 images without width and height
6 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.
1 checks passed
Cumulative Layout Shift: 0.054
0.054The layout barely moves while loading (CLS 0.054, good is under 0.1).
Images and page weight
Page weight: 2.1 MB in 61 requests
2.1 MBYour homepage downloads 2.1 MB in 61 requests on a phone: images 1.5 MB (18), scripts 317 KiB (24) and fonts 123 KiB (1). Under 2 MB keeps phones on slow connections fast.
About 0.6 g of CO₂ per visit
0.59 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.59 g of CO₂e: 70.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
<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.
14 images without alt text
14 images have no alt text, which hurts accessibility and image search.
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.
Orphan list items
Some list items are not inside a list.
7 text elements with low contrast
7 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Definition list items are not wrapped in <dl> elements
Definition list items are not wrapped in <dl> elements (4 elements).
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
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
2 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 6 WCAG 2.2 A/AA and best-practice rules on the phone render: 2 passed and 4 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
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 short (33 characters)
Your meta description is only 33 characters: “Sunnylove Baby Products Co., Ltd.”. 70 to 160 characters is enough to sell the click.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
9 links crawlers can't follow
9 links have no real href, so search engines can't follow them.
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
87 internal links, 5 external
The homepage links to 87 pages on sunnylove.com.cn and 5 external pages.
4 checks passed
Title: 33 characters
Your title is a healthy 33 characters: “Sunnylove Baby Products Co., Ltd.”.
Canonical URL set
The canonical URL is http://www.sunnylove.com.cn/index.html.
robots.txt in place
robots.txt is in place.
XML sitemap found
Your XML sitemap is reachable at https://sunnylove.com.cn/sitemap.xml.
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://sunnylove.com.cn/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
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.
Other pages
4 pages share a title
/, https://sunnylove.com.cn/product.html, https://sunnylove.com.cn/news.html and https://sunnylove.com.cn/displaynews.html all use the title “Sunnylove Baby Products Co., Ltd.”. Search engines can't tell which page to show for a search, so each competes with the others.
1 page without a meta description
https://sunnylove.com.cn/page.html has no meta description, so Google writes the search snippet from whatever text it finds.
3 pages share a meta description
https://sunnylove.com.cn/product.html, https://sunnylove.com.cn/news.html and https://sunnylove.com.cn/displaynews.html use the same meta description. A description written for each page earns more clicks.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://sunnylove.com.cn/cn/index.html, whose canonical is https://sunnylove.com.cn/index.html. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
5 pages without an H1
https://sunnylove.com.cn/cn/index.html, https://sunnylove.com.cn/page.html, https://sunnylove.com.cn/product.html, https://sunnylove.com.cn/news.html and https://sunnylove.com.cn/displaynews.html have no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://sunnylove.com.cn/cn/index.html 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.
5 internal pages checked
We fetched 5 pages linked from your homepage and read each the way a search engine does.
3 checks passed
Linked pages load
All 5 pages we checked loaded without an error.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 5 pages that loaded have a <title>.
Best practices
No mobile viewport
No viewport meta tag, so phones render the desktop layout zoomed out.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).
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.
Thin social proof
Social proof on the homepage: 1 testimonial or review block. Pairing it with named testimonials or customer logos makes it far more convincing.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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 268 words of copy
The homepage carries about 268 words of visible text.
2 checks passed
5 calls to action
The homepage has 5 calls to action, for example “Contact us”, “Contact Us” and “Contact information”.
1 short form
A short form (1 field at most) is right on the homepage.
Privacy and tracking
2 cookies set on arrival
2Opening the homepage sets 2 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 sunnylove.com.cn, 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
- CTGNet
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 49 issues on sunnylove.com.cn, including 21 speed issues, 6 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.