Website review, no card needed

kasep.co.id logo

kasep.co.id website review

Visit site (opens in a new tab)Reviewed 6 November 202624 issues · 76 checks

This review found 24 issues worth fixing on kasep.co.id, 8 of them high impact, across 76 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
1.1 s987 msJul 4Oct 311.0 s
Show as table
DateReal-visitor load time (LCP)
Jul 4, 20261.1 s
Jul 11, 20261.1 s
Jul 18, 20261.1 s
Jul 25, 20261.1 s
Oct 31, 20261.0 s

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

Full-page screenshot of kasep.co.id (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. kasep.co.id at 0.4 s0.4 s
  2. kasep.co.id at 0.8 s0.8 s
  3. kasep.co.id at 1.1 s1.1 s
  4. kasep.co.id at 1.5 s1.5 s
  5. kasep.co.id at 1.9 s1.9 s
  6. kasep.co.id at 2.3 s2.3 s
  7. kasep.co.id at 2.6 s2.6 s
  8. kasep.co.id at 3.0 s3.0 s

Speed

3 to fix75
  • Render-blocking requests

    1.1 s

    10 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.

  • Mobile performance score: 75

    75/100

    Your mobile performance score is 75. Pages that score under 90 lose visitors before the first paint.

  • Reduce unused JavaScript

    580 ms · 107 KiB

    About 107 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 580 ms faster on a phone.

  • Improve image delivery

    250 ms · 191 KiB

    12 images could be 191 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 250 ms faster on a phone.

  • 2 third-party services on the page

    2 third-party services load with your homepage (Shopify and oxiapps.com), adding 256 KiB and 102 ms of main-thread time.

  • 2 long tasks on the main thread

    2 long tasks block the main thread while loading, the longest for 64 ms. During a long task the page ignores taps.

  • 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.

  • Duplicated JavaScript

    5 KiB

    5 KiB JavaScript is shipped twice across bundles.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

  • Use efficient cache lifetimes

    1 KiB

    1 file is served with short cache lifetimes, so returning visitors download them again (1 KiB).

2 checks passed
  • Main-thread work: 1.2 s

    A phone's processor spends 1.2 s on main-thread work while loading, 258 ms of it running JavaScript. That is comfortably low.

  • Server response: 6 ms

    6 ms

    Your server sent the HTML in 6 ms, well inside Google's 600 ms guideline.

Core Web Vitals

2 to fix100
  • Largest Contentful Paint: 7.8 s

    7.8 s

    Your largest element takes 7.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • Time to Interactive: 8.0 s

    8.0 s

    The page becomes fully interactive after 8.0 s. Good is under 3.8 s.

  • Largest content (LCP) held steady for real visitors

    -4%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.1 s to 1.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

10 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 1.0 s

    1.0 s

    Real visitors wait 1.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 105 ms

    105 ms

    Real visitors wait 105 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Real-user FCP: 0.6 s

    0.6 s

    Real visitors see the first content after 0.6 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 345 ms

    345 ms

    Real visitors wait 345 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Speed Index: 3.2 s

    3.2 s

    Visually, the page fills in at 3.2 s (Speed Index), inside the 3.4 s “good” threshold.

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

  • First Contentful Paint: 0.9 s

    0.9 s

    The first text or image appears after 0.9 s, inside the 1.8 s “good” threshold.

  • Total Blocking Time: 26 ms

    26 ms

    Scripts block the page for only 26 ms while loading. Good is under 200 ms.

Images and page weight

1 to fix85
  • Page weight: 2.5 MB in 252 requests

    2.5 MB

    Your homepage downloads 2.5 MB in 252 requests on a phone: images 1.2 MB (53), other files 879 KiB (124) and scripts 321 KiB (50). Under 2 MB keeps phones on slow connections fast.

  • About 0.7 g of CO₂ per visit

    0.71 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.71 g of CO₂e: 85.1 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

5 to fixGoogle 9392
  • Invalid ARIA attributes

    2 elements use ARIA attributes their role does not allow, which confuses screen readers.

  • [role="img"] and [role="image"] elements must have alternative text (21 elements)

    [role="img"] and [role="image"] elements must have alternative text: 21 elements on the page fail this check, rated serious by axe-core.

  • All page content should be contained by landmarks (6 elements)

    All page content should be contained by landmarks: 6 elements on the page fail this check, rated moderate by axe-core.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

  • 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.

  • Headings skip levels

    Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 109 images in the HTML carry an alt attribute.

  • 38 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 44 WCAG 2.2 A/AA and best-practice rules on the phone render: 38 passed and 6 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 10083
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is short (22 characters)

    Your title is only 22 characters: “Kasep – Kasep Official”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 58 internal links, 7 external

    The homepage links to 58 pages on kasep.co.id and 7 external pages.

6 checks passed
  • Meta description: 142 characters

    Your meta description is 142 characters: “Temukan inspirasi fashion terbaru dari Kasep & Kasep Selected. Dapatkan rangkaian pilihan produk dengan kualitas terbai…”.

  • Canonical URL set

    The canonical URL is https://kasep.co.id/.

  • Structured data in place

    Structured data found: BreadcrumbList, 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://kasep.co.id/sitemap.xml.

AI search readiness

1 to fix88
  • Organization data is thin (2 of 6 facts)

    Your Organization JSON-LD is missing logo, 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.

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.

  • Text is in the HTML

    Your server sends the page's text in the HTML (394 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://kasep.co.id/llms.txt (5 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

4 to fix60
  • 1 linked page is broken

    Your homepage links to https://kasep.co.id/[email protected], which answers with an error. Visitors hit a dead end and search engines drop it.

  • 8 pages without a meta description

    https://kasep.co.id/pages/kasep-selected, https://kasep.co.id/collections/shop-all, https://kasep.co.id/collections/new-arrivals, https://kasep.co.id/collections/shop-all-selected, https://kasep.co.id/collections/top and https://kasep.co.id/collections/bottom and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 5 links to non-canonical URLs

    Your homepage links to 5 pages by a URL that isn't their canonical one, for example https://kasep.co.id/collections/deals/products/lingga-koko, whose canonical is https://kasep.co.id/products/lingga-koko. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 1 page without an H1

    https://kasep.co.id/pages/kasep-selected has no <h1> headline, so visitors and search engines get no clear main topic.

  • 8 pages slow to respond

    https://kasep.co.id/pages/kasep-selected, https://kasep.co.id/collections/new-arrivals, https://kasep.co.id/collections/shop-all-selected, https://kasep.co.id/collections, https://kasep.co.id/collections/top and https://kasep.co.id/collections/bottom and 2 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 37 found) and read each the way a search engine does.

3 checks passed
  • 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 14 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9678
  • 1 broken image

    1 image failed to load on a phone, for example https://kasep.co.id/cdn/shop/files/KASEP_WEBSITE-9TH_ANNIV_DEALS_Mobile_1500x1990_f43a4c20-940b-480d-aea2-61aace469edc.jpg?v=1793464992&width=360.

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'querySelector')”.

2 checks passed
  • Tap targets are thumb-sized

    20 of 23 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix75
  • Thin social proof

    Social proof on the homepage: 1 trust badge. 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.

  • 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 333 words of copy

    The homepage carries about 333 words of visible text.

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SHOP NOW”.

  • 4 calls to action

    The homepage has 4 calls to action, for example “SHOP ALL”, “SHOP NOW” and “Shop NOw”.

  • 4 short forms

    4 short forms (1 field at most) are right on the homepage, asking for an email.

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads Meta Pixel (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.

  • 6 cookies set on arrival

    6

    Opening the homepage sets 6 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.

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 kasep.co.id, 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 2 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Oxi Social Login Wishlist · Tek Labs Gifts Upsell

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
Shopify

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 24 issues on kasep.co.id, including 5 speed issues, 2 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25