Website review, no card needed
lilabc.com website review
Visit site (opens in a new tab)Reviewed 18 November 202628 issues · 69 checks
This review found 28 issues worth fixing on lilabc.com, 8 of them high impact, across 69 checks. The most urgent: 1 linked page is broken. 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
74C- #84,037 of 119,846 reviewed websitesbeats 26%
- #53,146 of 67,947 online storesbeats 18%
- #50,001 of 61,930 Shopify storesbeats 16%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Jul 18, 2026 | 3.5 s |
| Jul 25, 2026 | 3.2 s |
| Aug 1, 2026 | 3.0 s |
| Aug 8, 2026 | 3.0 s |
| Aug 15, 2026 | 2.9 s |
| Aug 22, 2026 | 2.9 s |
| Aug 29, 2026 | 2.9 s |
| Sep 5, 2026 | 2.9 s |
| Sep 12, 2026 | 2.9 s |
| Sep 19, 2026 | 3.2 s |
| Sep 26, 2026 | 3.2 s |
| Oct 3, 2026 | 3.2 s |
| Oct 10, 2026 | 3.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Jul 18, 2026 | 206 ms |
| Jul 25, 2026 | 196 ms |
| Aug 1, 2026 | 184 ms |
| Aug 8, 2026 | 182 ms |
| Aug 15, 2026 | 176 ms |
| Aug 22, 2026 | 174 ms |
| Aug 29, 2026 | 174 ms |
| Sep 5, 2026 | 168 ms |
| Sep 12, 2026 | 172 ms |
| Sep 19, 2026 | 220 ms |
| Sep 26, 2026 | 229 ms |
| Oct 3, 2026 | 234 ms |
| Oct 10, 2026 | 238 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
Use efficient cache lifetimes
750 ms · 1.0 MB71 files are served with short cache lifetimes, so returning visitors download them again (1.0 MB).
Mobile performance score: 68
68/100Your mobile performance score is 68. Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
420 ms · 559 KiBAbout 559 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 420 ms faster on a phone.
Render-blocking requests
700 ms5 files block the first paint until they finish downloading. Deferring or inlining them could save about 700 ms.
Improve image delivery
300 ms · 150 KiB7 images could be 150 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.
Main-thread work: 3.0 s
A phone's processor spends 3.0 s on main-thread work while loading, 1.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
2,380 HTML elements
The page has 2,380 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
8 third-party services on the page
8 third-party services load with your homepage (Facebook, Clarity and Klaviyo and others), adding 380 KiB and 345 ms of main-thread time.
Reduce unused CSS
270 ms · 60 KiBAbout 60 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 270 ms faster on a phone.
9 long tasks on the main thread
9 long tasks block the main thread while loading, the longest for 110 ms. During a long task the page ignores taps.
Legacy JavaScript
40 KiBPolyfills for old browsers add 40 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.
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: 298 ms
298 msYour server sent the HTML in 298 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 15.5 s
15.5 sThe page becomes fully interactive after 15.5 s. Good is under 3.8 s.
Speed Index: 8.1 s
8.1 sVisually, the page fills in at 8.1 s (Speed Index). Good is under 3.4 s.
Largest Contentful Paint: 5.3 s
5.3 sYour largest element takes 5.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “RAJAPLAY: Arena Pemburu Maxwin Paling Dicari!”. Most of its time is element render delay (2.6 s).
First Contentful Paint: 1.9 s
1.9 sThe first text or image appears after 1.9 s on a phone. Good is under 1.8 s.
Total Blocking Time: 204 ms
204 msScripts block taps and scrolling for 204 ms in total while the page loads. Good is under 200 ms.
2 images without width and height
2 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 17% slower for real visitors
+17%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 206 ms to 238 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-1%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 3.5 s to 3.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
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.013
0.013The layout barely moves while loading (CLS 0.013, good is under 0.1).
Images and page weight
Page weight: 2.2 MB in 150 requests
2.2 MBYour homepage downloads 2.2 MB in 150 requests on a phone: scripts 1.6 MB (97), images 246 KiB (11) and other files 137 KiB (24). Under 2 MB keeps phones on slow connections fast.
About 0.6 g of CO₂ per visit
0.63 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.63 g of CO₂e: 75.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
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
22 text elements with low contrast
22 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
<marquee> elements are deprecated and must not be used (1 element)
<marquee> elements are deprecated and must not be used: 1 element on the page fails this check, rated serious by axe-core.
All page content should be contained by landmarks (7 elements)
All page content should be contained by landmarks: 7 elements on the page fail this check, rated moderate by axe-core.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
Alternative text of images should not be repeated as text (5 elements)
Alternative text of images should not be repeated as text: 5 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h1 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 131 images in the HTML carry an alt attribute.
46 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 6 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
2 H1 headlines
There are 2 <h1> headlines (“RAJAPLAY: Arena Pemburu Maxwin Paling Dicari!” and “RAJAPLAY: Arena Pemburu Maxwin Paling Dicari!”). One clear main headline is easier for people and search engines.
117 internal links, 7 external
The homepage links to 117 pages on lilabc.com and 7 external pages.
7 checks passed
Meta description: 160 characters
Your meta description is 160 characters: “RAJAPLAY menghadirkan arena terbaik bagi para pemburu maxwin dengan sistem stabil & berbagai pilihan permainan menarik …”.
Title: 45 characters
Your title is a healthy 45 characters: “RAJAPLAY: Arena Pemburu Maxwin Paling Dicari!”.
Canonical URL set
The canonical URL is https://puntodiez.net/.
Structured data in place
Structured data found: Article, BreadcrumbList, FAQPage, Product and ProductGroup.
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://puntodiez.net/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://puntodiez.net/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.
Opted out of AI training for 5 crawlers
robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.
2 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.
Text is in the HTML
Your server sends the page's text in the HTML (2,308 words), so crawlers that don't run JavaScript still read it.
Other pages
1 linked page is broken
Your homepage links to https://puntodiez.net/collections/vendors, which answers with an error. Visitors hit a dead end and search engines drop it.
1 internal page checked
We fetched 1 page linked from your homepage and read each the way a search engine does.
Best practices
2 broken images
2 images failed to load on a phone, for example https://bat.bing.com/action/0?ti=56337638&Ver=2&mid=c3fe0902-1b81-42b9-8661-5ede7a80e1ae&bo=1&sid=9f197ef0e39811f19d8325af21e7b861&vid=9f197e00e39811f1b99b3d723d5d3691&vids=1&msclkid=N&pi=918639831&lg.
7 small tap targets
7 of 24 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “Uncaught TypeError: Cannot read properties of undefined (reading 'checkout')”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
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 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 621 words of copy
The homepage carries about 621 words of visible text.
4 checks passed
4 calls to action
The homepage has 4 calls to action, for example “JOIN NOW”, “Contact Us” and “Where to Buy”.
4 short forms
4 short forms (3 fields at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 2 testimonial or review blocks and a star rating.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics, Microsoft Clarity and Cloudflare Web Analytics.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Tag Manager, Klaviyo, Meta Pixel, Microsoft Ads and Microsoft Clarity (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.
12 cookies set on arrival
12Opening the homepage sets 12 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.
19 other companies contacted
Loading the homepage contacts 19 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 lilabc.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 11 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Simprosys Google Shopping Feed · Beans Id Verification · Okendo · Klaviyo Email Marketing Sms · Uppromote Affiliate · Smart Seo · Swish App · trafficmanager.net · amazonaws.com · herokuapp.com · shgcdn3.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
- jQuery
- E-commerce
- Shopify
- Analytics
- Google Analytics | Google Tag Manager | Microsoft Clarity
- Hosting
- Cloudflare
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 28 issues on lilabc.com, including 13 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.