Website review, no card needed
sunlu.com website review
Visit site (opens in a new tab)Reviewed 4 November 202632 issues · 82 checks
This review found 32 issues worth fixing on sunlu.com, 9 of them high impact, across 82 checks. The most urgent: reduce unused JavaScript. 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
82B- #25,233 of 90,285 reviewed websitesbeats 67%
- #15,758 of 47,388 online storesbeats 60%
- #15,164 of 42,609 Shopify storesbeats 57%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 4.6 s |
| May 23, 2026 | 5.2 s |
| May 30, 2026 | 4.5 s |
| Jun 6, 2026 | 4.0 s |
| Jun 13, 2026 | 3.7 s |
| Jun 20, 2026 | 3.5 s |
| Jun 27, 2026 | 3.3 s |
| Jul 4, 2026 | 3.1 s |
| Jul 11, 2026 | 2.8 s |
| Jul 18, 2026 | 2.7 s |
| Jul 25, 2026 | 2.5 s |
| Aug 1, 2026 | 2.6 s |
| Aug 8, 2026 | 2.6 s |
| Aug 15, 2026 | 2.6 s |
| Aug 22, 2026 | 2.6 s |
| Aug 29, 2026 | 2.6 s |
| Sep 5, 2026 | 2.5 s |
| Sep 12, 2026 | 2.5 s |
| Sep 19, 2026 | 2.5 s |
| Sep 26, 2026 | 2.6 s |
| Oct 3, 2026 | 2.6 s |
| Oct 10, 2026 | 2.6 s |
| Oct 17, 2026 | 2.6 s |
| Oct 24, 2026 | 2.6 s |
| Oct 31, 2026 | 2.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 112 ms |
| May 23, 2026 | 112 ms |
| May 30, 2026 | 112 ms |
| Jun 6, 2026 | 112 ms |
| Jun 13, 2026 | 110 ms |
| Jun 20, 2026 | 107 ms |
| Jun 27, 2026 | 104 ms |
| Jul 4, 2026 | 102 ms |
| Jul 11, 2026 | 99 ms |
| Jul 18, 2026 | 97 ms |
| Jul 25, 2026 | 96 ms |
| Aug 1, 2026 | 98 ms |
| Aug 8, 2026 | 101 ms |
| Aug 15, 2026 | 102 ms |
| Aug 22, 2026 | 103 ms |
| Aug 29, 2026 | 103 ms |
| Sep 5, 2026 | 100 ms |
| Sep 12, 2026 | 100 ms |
| Sep 19, 2026 | 97 ms |
| Sep 26, 2026 | 96 ms |
| Oct 3, 2026 | 96 ms |
| Oct 10, 2026 | 96 ms |
| Oct 17, 2026 | 96 ms |
| Oct 24, 2026 | 96 ms |
| Oct 31, 2026 | 96 ms |
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
Speed
Reduce unused JavaScript
5.3 s · 1.0 MBAbout 1.0 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.3 s faster on a phone.
Mobile performance score: 47
47/100Your mobile performance score is 47. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Use efficient cache lifetimes
650 ms · 133 KiB36 files are served with short cache lifetimes, so returning visitors download them again (133 KiB).
Render-blocking requests
600 ms15 files block the first paint until they finish downloading. Deferring or inlining them could save about 600 ms.
Google Tag Manager adds 288 ms
288 msGoogle Tag Manager costs a phone 288 ms of main-thread work and 296 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.2 s
A phone's processor spends 2.2 s on main-thread work while loading, 936 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
2 third-party services on the page
2 third-party services load with your homepage (Google Tag Manager and Google Analytics), adding 297 KiB and 288 ms of main-thread time.
12 long tasks on the main thread
12 long tasks block the main thread while loading, the longest for 221 ms. During a long task the page ignores taps.
Reduce unused CSS
150 ms · 29 KiBAbout 29 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
Improve image delivery
19 KiB2 images could be 19 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
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: 4 ms
4 msYour server sent the HTML in 4 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.
Largest Contentful Paint: 14.8 s
14.8 sYour largest element takes 14.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “SUNLU Banner”.
Time to Interactive: 14.8 s
14.8 sThe page becomes fully interactive after 14.8 s. Good is under 3.8 s.
Speed Index: 7.0 s
7.0 sVisually, the page fills in at 7.0 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.5 s
3.5 sThe first text or image appears after 3.5 s on a phone. Good is under 1.8 s.
Real-user FCP: 2.0 s
2.0 sReal visitors see the first content after 2.0 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.6 s
1.6 sReal visitors wait 1.6 s for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 591 ms
591 msScripts block taps and scrolling for 591 ms in total while the page loads. Good is under 200 ms.
6 checks passed
Real-user LCP: 2.4 s
2.4 sReal visitors wait 2.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 97 ms
97 msReal visitors wait 97 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.07
0.07For real visitors the layout shifts by 0.07 (75th percentile). Good is under 0.1.
Tap response (INP) got 14% faster for real visitors
-14%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 112 ms to 96 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 47% faster for real visitors
-47%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 4.6 s to 2.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 2.4 MB in 84 requests
2.4 MBYour homepage downloads 2.4 MB in 84 requests on a phone: scripts 1.5 MB (22), images 550 KiB (15) and other files 269 KiB (30). Under 2 MB keeps phones on slow connections fast.
1 image in older formats
1 image (123 KiB) 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.
About 0.7 g of CO₂ per visit
0.69 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.69 g of CO₂e: 82.7 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
ARIA roles used must conform to valid values (2 elements)
ARIA roles used must conform to valid values: 2 elements on the page fail this check, rated critical by axe-core.
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
3 form fields without a label
3 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings should not be empty (2 elements)
Headings should not be empty: 2 elements on the page fail this check, rated minor by axe-core.
Alternative text of images should not be repeated as text (1 element)
Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 11 images in the HTML carry an alt attribute.
40 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 46 WCAG 2.2 A/AA and best-practice rules on the phone render: 40 passed and 6 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 (93 characters)
Your title is 93 characters, so Google will cut it off around 60: “SUNLU - Leading 3D Printing Materials Supplier | 3D Printer Filament, Resin & Dryer Solut…”.
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.
2 links with vague text
2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
30 internal links, 10 external
The homepage links to 30 pages on sunlu.com and 10 external pages.
6 checks passed
Meta description: 154 characters
Your meta description is 154 characters: “As a leading 3D printer filament supplier, SUNLU offers premium PLA filament, resins, and advanced filament dryers to e…”.
One H1 headline
Your main headline reads: “SUNLU Official Website”.
Canonical URL set
The canonical URL is https://www.sunlu.com/.
Structured data in place
Structured data found: ItemList, Organization and WebSite.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://www.sunlu.com/sitemap.xml.
AI search readiness
No llms.txt
There is no /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.
3 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.
Organization data: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
Text is in the HTML
Your server sends the page's text in the HTML (680 words), so crawlers that don't run JavaScript still read it.
Other pages
10 pages share a title
/, /community, /materials-lab/color-aesthetics, /materials-lab/application-scenarios, /materials-lab/printer-presets and /materials-lab/extreme-test-zone and 4 others all use the title “SUNLU - Leading 3D Printing Materials Supplier | 3D Printer Filament,…”. Search engines can't tell which page to show for a search, so each competes with the others.
10 pages share a meta description
/community, /materials-lab/color-aesthetics, /materials-lab/application-scenarios, /materials-lab/printer-presets, /materials-lab/material-comparison and /materials-lab/extreme-test-zone and 4 others use the same meta description. A description written for each page earns more clicks.
6 pages without an H1
/community, /materials-lab/color-aesthetics, /materials-lab/printer-presets, /materials-lab/material-comparison, /materials-lab/extreme-test-zone and /match-ai have no <h1> headline, so visitors and search engines get no clear main topic.
6 pages with very little text
/community, /materials-lab/color-aesthetics, /materials-lab/application-scenarios, /materials-lab/printer-presets, /materials-lab/extreme-test-zone and /match-ai 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.
9 pages slow to respond
/collections/1, /collections/2, /materials-lab/application-scenarios, /materials-lab/material-comparison, /materials-lab/extreme-test-zone and /match-ai and 3 others took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 22 found) and read each the way a search engine does.
5 checks passed
Linked pages load
13 pages of 15 loaded without an error (the rest turned automated requests away).
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 13 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 13 pages that loaded have a <title>.
Best practices
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Hydration completed but contains mismatches.”.
Missing source maps
Large scripts ship without source maps.
2 checks passed
Tap targets are thumb-sized
11 of 11 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 232 words
The homepage has only about 232 words of visible text; thin pages give Google and first-time buyers little to go on.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Learn more”.
11 calls to action
The homepage has 11 calls to action, for example “Learn more”, “Subscribe” and “Contact us”.
1 short form
A short form (1 field at most) is right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 8 testimonial or review blocks and 1 trust badge.
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
1 tracker load before any consent
1Before a visitor clicks anything, the page loads Google Tag Manager (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.
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.
1 other company contacted
Loading the homepage contacts 1 host 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 sunlu.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
- Nuxt
- E-commerce
- Shopify;Shopify Plus
- Hosting
- Alibaba Cloud
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 32 issues on sunlu.com, including 14 speed issues, 3 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.