Website review, no card needed
aandcllp.com website review
Visit site (opens in a new tab)Reviewed 17 November 202638 issues · 86 checks
This review found 38 issues worth fixing on aandcllp.com, 15 of them high impact, across 86 checks. The most urgent: render-blocking requests. 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
71C- #94,335 of 116,487 reviewed websitesbeats 16%
- #58,635 of 66,776 online storesbeats 10%
- #54,552 of 60,929 Shopify storesbeats 9%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Oct 10, 2026 | 2.2 s |
| Oct 17, 2026 | 2.3 s |
| Oct 24, 2026 | 2.3 s |
| Oct 31, 2026 | 2.3 s |
| Nov 7, 2026 | 2.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Oct 10, 2026 | 171 ms |
| Oct 17, 2026 | 178 ms |
| Oct 24, 2026 | 173 ms |
| Oct 31, 2026 | 173 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
How it loaded on a phone
0.7 s
1.5 s
2.2 s
3.0 s
3.7 s
4.4 s
5.2 s
5.9 s
Speed
Render-blocking requests
2.1 s37 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.1 s.
Reduce unused JavaScript
1.5 s · 290 KiBAbout 290 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.5 s faster on a phone.
Main-thread work: 4.1 s
A phone's processor spends 4.1 s on main-thread work while loading, 376 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Reduce unused CSS
910 ms · 1.6 MBAbout 1.6 MB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 910 ms faster on a phone.
Improve image delivery
150 ms · 2.3 MB5 images could be 2.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (istudiosg.com, Cloudflare and Yellow Robot and others), adding 6.0 MB and 435 ms of main-thread time.
Mobile performance score: 63
63/100Your mobile performance score is 63. Pages that score under 90 lose visitors before the first paint.
Use efficient cache lifetimes
600 ms · 112 KiB8 files are served with short cache lifetimes, so returning visitors download them again (112 KiB).
istudiosg.com adds 372 ms
372 msistudiosg.com costs a phone 372 ms of main-thread work and 1.3 MB 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.
b-cdn.net adds 0 ms
0 msb-cdn.net costs a phone 0 ms of main-thread work and 4.5 MB 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.
1,737 HTML elements
The page has 1,737 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Legacy JavaScript
150 ms · 21 KiBPolyfills for old browsers add 21 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Minify CSS
150 ms · 13 KiB13 KiB could be saved by minifying CSS.
5 long tasks on the main thread
5 long tasks block the main thread while loading, the longest for 136 ms. During a long task the page ignores taps.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
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.
Minify JavaScript
2 KiB2 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 6 ms
6 msYour server sent the HTML in 6 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 24.3 s
24.3 sYour largest element takes 24.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 24.3 s
24.3 sThe page becomes fully interactive after 24.3 s. Good is under 3.8 s.
First Contentful Paint: 3.1 s
3.1 sThe first text or image appears after 3.1 s on a phone. Good is under 1.8 s.
Speed Index: 5.6 s
5.6 sVisually, the page fills in at 5.6 s (Speed Index). Good is under 3.4 s.
4 images without width and height
4 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
-1%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 171 ms to 173 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 12% slower for real visitors
+12%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 2.2 s to 2.7 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.
2 checks passed
Total Blocking Time: 142 ms
142 msScripts block the page for only 142 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 6.4 MB in 130 requests
6.4 MBYour homepage downloads 6.4 MB in 130 requests on a phone: images 4.6 MB (20), scripts 691 KiB (39) and fonts 569 KiB (6). Under 2 MB keeps phones on slow connections fast.
2 images over 500 KB
2 images weigh 4.3 MB together. On a phone connection a single image that size takes seconds.
1 image far larger than shown
2.1 MB1 image is downloaded at several times the size a phone draws it, for example keluarkansgpdlusekakwrerw.png at 1,672 px wide, shown at 84 px. Resized copies would save about 2.1 MB.
3 images in older formats
3 images (4.4 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 1.8 g of CO₂ per visit
1.80 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.80 g of CO₂e: 216.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
Elements must only use permitted ARIA attributes (3 elements)
Elements must only use permitted ARIA attributes: 3 elements on the page fail this check, rated serious by axe-core.
3 text elements with low contrast
3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
2 tap targets too small
2 tap targets are too small or too close together to hit reliably with a finger.
4 images without alt text
4 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
2 links without text
2 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h1 → h3, h1 → h3 and h1 → h3), which makes the page harder to scan with a screen reader.
1 checks passed
49 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 56 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 7 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (77 characters)
Your title is 77 characters, so Google will cut it off around 60: “Kudaslot: Jelajah Wisata Kuliner Terbaik & Rekomendasi Pasaran SGP Terfavorit”.
10 H1 headlines
There are 10 <h1> headlines (“Kudaslot: Jelajah Wisata Kuliner Terbaik & Rekome…”, “Kudaslot: Jelajah Wisata Kuliner Terbaik & Rekome…” and “Kudaslot: Jelajah Wisata Kuliner Terbaik & Rekome…”). One clear main headline is easier for people and search engines.
No XML sitemap
No XML sitemap at https://kudaaslottt.com/sitemap.xml, so Google discovers your pages only by following links.
3 links crawlers can't follow
3 links have no real href, so search engines can't follow them.
102 internal links, 18 external
The homepage links to 102 pages on aandcllp.com and 18 external pages.
5 checks passed
Meta description: 145 characters
Your meta description is 145 characters: “Kudaslot menghadirkan informasi wisata kuliner menarik, rekomendasi tempat makan populer, serta beragam Pasaran Terleng…”.
Canonical URL set
The canonical URL is https://kudaaslottt.com/register/.
Structured data in place
Structured data found: BreadcrumbList, FAQPage, Organization, Product and SoftwareApplication.
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.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
No llms.txt
There is no https://kudaaslottt.com/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.
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,082 words), so crawlers that don't run JavaScript still read it.
Other pages
14 linked pages are broken
Your homepage links to https://kudaaslottt.com/policies/shipping-policy, https://kudaaslottt.com/pages/applecare-landing-page, https://kudaaslottt.com/pages/limited-time-promotion, https://kudaaslottt.com/products/iphone-17-pro-mg8h4x-a, https://kudaaslottt.com/pages/applecare and https://kudaaslottt.com/pages/business-solutions and 8 others, which answer with an error. Visitors hit a dead end and search engines drop them.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://kudaaslottt.com/amp, whose canonical is https://kudaaslottt.com/register. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
1 page with very little text
https://kudaaslottt.com/amp 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.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 25 found) and read each the way a search engine does.
5 checks passed
Every page has a meta description
All 1 page that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
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 1 page that loaded have a <title>.
Best practices
11 small tap targets
11 of 40 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 “Mixed Content: The page at 'https://kudaaslottt.com/register/' was loaded over HTTPS, but requested an insecure stylesh…”.
24 distorted images
24 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
Requests the geolocation permission on page load
Requests the geolocation permission on page load.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
Browser-reported issues
Chrome logged issues while loading the page (“Mixed content”).
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 1,098 words of copy
The homepage carries about 1,098 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
4 checks passed
5 calls to action
The homepage has 5 calls to action, for example “Buy It Now”, “Contact Us” and “Why Shop at iStudio”.
4 short forms
4 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 1 testimonial or review block, 4 customer or partner logos, a star rating and 1 trust badge.
Analytics in place
Analytics detected: Cloudflare Web Analytics.
Privacy and tracking
1 cookie set on arrival
1Opening the homepage sets 1 cookie (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.
11 other companies contacted
Loading the homepage contacts 11 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 aandcllp.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 1 app. It is code from another company running for your shoppers.
Apps your storefront loads
backinstock.org
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
- E-commerce
- Shopify
- Hosting
- Cloudflare
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 38 issues on aandcllp.com, including 16 speed issues, 4 SEO issues 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.