Website review, no card needed
fillerx.com website review
Visit site (opens in a new tab)Reviewed 11 November 202614 issues · 59 checks
This review found 14 issues worth fixing on fillerx.com, 3 of them high impact, across 59 checks. The most urgent: fails Core Web Vitals for real visitors. Google's speed test didn't respond, so speed is not measured here; your full playbook measures it. 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
Not scored yet: Google's speed test didn't run in this review. Re-run the review to get a score.
Show as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 2.1 s |
| May 30, 2026 | 2.0 s |
| Jun 6, 2026 | 2.0 s |
| Jun 13, 2026 | 1.9 s |
| Jun 20, 2026 | 1.9 s |
| Jun 27, 2026 | 1.9 s |
| Jul 4, 2026 | 2.0 s |
| Jul 11, 2026 | 2.0 s |
| Jul 18, 2026 | 1.9 s |
| Jul 25, 2026 | 1.9 s |
| Aug 1, 2026 | 1.8 s |
| Aug 8, 2026 | 1.7 s |
| Aug 15, 2026 | 1.8 s |
| Aug 22, 2026 | 1.8 s |
| Aug 29, 2026 | 1.8 s |
| Sep 5, 2026 | 1.9 s |
| Sep 12, 2026 | 1.9 s |
| Sep 19, 2026 | 1.9 s |
| Sep 26, 2026 | 2.0 s |
| Oct 3, 2026 | 1.9 s |
| Oct 10, 2026 | 1.9 s |
| Oct 17, 2026 | 1.8 s |
| Oct 24, 2026 | 1.8 s |
| Oct 31, 2026 | 1.8 s |
| Nov 7, 2026 | 1.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 254 ms |
| May 30, 2026 | 263 ms |
| Jun 6, 2026 | 235 ms |
| Jun 13, 2026 | 228 ms |
| Jun 20, 2026 | 219 ms |
| Jun 27, 2026 | 218 ms |
| Jul 4, 2026 | 232 ms |
| Jul 11, 2026 | 237 ms |
| Jul 18, 2026 | 245 ms |
| Jul 25, 2026 | 246 ms |
| Aug 1, 2026 | 235 ms |
| Aug 8, 2026 | 224 ms |
| Aug 15, 2026 | 220 ms |
| Aug 22, 2026 | 216 ms |
| Aug 29, 2026 | 219 ms |
| Sep 5, 2026 | 239 ms |
| Sep 12, 2026 | 240 ms |
| Sep 19, 2026 | 241 ms |
| Sep 26, 2026 | 268 ms |
| Oct 3, 2026 | 257 ms |
| Oct 10, 2026 | 256 ms |
| Oct 17, 2026 | 255 ms |
| Oct 24, 2026 | 231 ms |
| Oct 31, 2026 | 212 ms |
| Nov 7, 2026 | 215 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
Not measured in this review.
Core Web Vitals
Fails Core Web Vitals for real visitors
Real Chrome users on phones do not pass Google's Core Web Vitals on your site (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.
Real-user INP: 212 ms
212 msReal visitors wait 212 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user TTFB: 810 ms
810 msReal visitors wait 810 ms for your server to start answering (75th percentile). Good is under 800 ms.
5 checks passed
Real-user LCP: 1.9 s
1.9 sReal visitors wait 1.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
Real-user FCP: 1.4 s
1.4 sReal visitors see the first content after 1.4 s (75th percentile). Good is under 1.8 s.
Tap response (INP) got 17% faster for real visitors
-17%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 254 ms to 215 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 11% faster for real visitors
-11%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 2.1 s to 1.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
Page weight: 6.0 MB
6.0 MBYour homepage downloads 6.0 MB on a phone, 960 KiB of it images (16%). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
banner35.webp is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
1 image below the first screen load straight away
1 image further down the page (21 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 1.7 g of CO₂ per visit
1.69 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.69 g of CO₂e: 203.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
9 images without alt text
9 images have no alt text, which hurts accessibility and image search.
51 form fields without a label
51 form fields have no label, so screen readers announce an empty box and autofill guesses.
20 links without text
20 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h3 → h5), which makes the page harder to scan with a screen reader.
SEO
Meta description is long (293 characters)
Your meta description is 293 characters; Google truncates after about 160, so the end of your pitch is cut.
489 internal links, 32 external
The homepage links to 489 pages on fillerx.com and 32 external pages.
7 checks passed
One H1 headline
Your main headline reads: “Filler Lux”.
Title: 64 characters
Your title is a healthy 64 characters: “Shop Skinboosters, Microneedling & Korean Skincare at Filler Lux”.
Canonical URL set
The canonical URL is https://fillerx.com/.
Structured data in place
Structured data found: Organization and WebSite.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
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://fillerx.com/sitemap.xml.
AI search readiness
4 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: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and description; contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (3,100 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://fillerx.com/llms.txt (11 KiB, 37 links), a plain-text guide to the site for AI tools.
Other pages
3 pages without an H1
https://fillerx.com/blogs/news/meet-vt-cosmetics-korean-microneedling-skincare, https://fillerx.com/blogs/news/brmud-korean-mineral-mud-skincare-for-oily-skin-sebum-control and https://fillerx.com/products/rejuran-dual-effect-ampoule have no <h1> headline, so visitors and search engines get no clear main topic.
4 pages slow to respond
https://fillerx.com/collections/mise-en-scene, https://fillerx.com/blogs/news/meet-vt-cosmetics-korean-microneedling-skincare, https://fillerx.com/blogs/news/brmud-korean-mineral-mud-skincare-for-oily-skin-sebum-control and https://fillerx.com/products/rejuran-dual-effect-ampoule took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 186 found) and read each the way a search engine does.
6 checks passed
Linked pages load
5 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 5 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
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
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_TUNNEL_CONNECTION_FAILED”.
2 checks passed
Tap targets are thumb-sized
100 of 122 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
About 1,148 words of copy
The homepage carries about 1,148 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
7 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Shop Skin Boosters” and “Learn More”.
25 calls to action
The homepage has 25 calls to action, for example “Join LuxCoin Club”, “Buy More - Save More” and “Buy One Get One Free”.
42 short forms
42 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 13 testimonial or review blocks, 15 customer or partner logos and 6 trust badges.
Direct contact links
Visitors can reach you directly: 3 phone links and 1 email link.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
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
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 2 mores (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.
24 cookies set on arrival
24Opening the homepage sets 24 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.
48 other companies contacted
Loading the homepage contacts 48 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 fillerx.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Apps on your store
Your storefront loads 15 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Gorgias Live Chat Helpdesk · Uppromote Affiliate · Seowill Ai Seo · Klaviyo Email Marketing Sms · Sk Contact Form Builder · Sc Easy Redirects · Fbp Fast Bundle · Simprosys Google Shopping Feed · Affliate By Secomapp · Forms · Ecomsend · Deco Labels Badges · Fokkio Gift With Purchase · loox.io · nfcube.com
Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info
Upkeep, stack and company
Stack
- Framework
- Tailwind CSS
- E-commerce
- Shopify
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 14 issues on fillerx.com, including 3 speed issues, 1 SEO issue 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.