Website review, no card needed

kokuyocamlin.com logo

kokuyocamlin.com website review

Visit site (opens in a new tab)Reviewed 27 October 202634 issues · 81 checks

This review found 34 issues worth fixing on kokuyocamlin.com, 13 of them high impact, across 81 checks. The most urgent: improve image delivery. 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
4.3 s2.5 sMay 9Oct 242.7 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20263.5 s
May 16, 20263.5 s
May 23, 20263.6 s
May 30, 20263.7 s
Jun 6, 20263.6 s
Jun 13, 20263.6 s
Jun 20, 20263.6 s
Jun 27, 20263.8 s
Jul 4, 20264.0 s
Jul 11, 20264.1 s
Jul 18, 20264.0 s
Jul 25, 20263.8 s
Aug 1, 20263.6 s
Aug 8, 20263.4 s
Aug 15, 20263.2 s
Aug 22, 20263.0 s
Aug 29, 20262.9 s
Sep 5, 20262.9 s
Sep 12, 20263.0 s
Sep 19, 20263.0 s
Sep 26, 20263.0 s
Oct 3, 20262.8 s
Oct 10, 20262.7 s
Oct 17, 20262.7 s
Oct 24, 20262.7 s
Real-visitor tap response (INP)75th percentile, phones
197 ms164 msMay 9Oct 24193 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026168 ms
May 16, 2026170 ms
May 23, 2026174 ms
May 30, 2026173 ms
Jun 6, 2026175 ms
Jun 13, 2026175 ms
Jun 20, 2026177 ms
Jun 27, 2026179 ms
Jul 4, 2026181 ms
Jul 11, 2026178 ms
Jul 18, 2026173 ms
Jul 25, 2026175 ms
Aug 1, 2026174 ms
Aug 8, 2026178 ms
Aug 15, 2026181 ms
Aug 22, 2026184 ms
Aug 29, 2026187 ms
Sep 5, 2026186 ms
Sep 12, 2026188 ms
Sep 19, 2026188 ms
Sep 26, 2026187 ms
Oct 3, 2026189 ms
Oct 10, 2026189 ms
Oct 17, 2026190 ms
Oct 24, 2026193 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

Full-page screenshot of kokuyocamlin.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. kokuyocamlin.com at 3.7 s3.7 s
  2. kokuyocamlin.com at 7.3 s7.3 s
  3. kokuyocamlin.com at 11.0 s11.0 s
  4. kokuyocamlin.com at 14.6 s14.6 s
  5. kokuyocamlin.com at 18.3 s18.3 s
  6. kokuyocamlin.com at 21.9 s21.9 s
  7. kokuyocamlin.com at 25.6 s25.6 s
  8. kokuyocamlin.com at 29.2 s29.2 s

Speed

10 to fix58
  • Improve image delivery

    2.9 s · 5.8 MB

    41 images could be 5.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.9 s faster on a phone.

  • Reduce unused JavaScript

    1.5 s · 560 KiB

    About 560 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.

  • Render-blocking requests

    1.0 s

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 1.0 s.

  • Use efficient cache lifetimes

    800 ms · 217 KiB

    5 files are served with short cache lifetimes, so returning visitors download them again (217 KiB).

  • Mobile performance score: 58

    58/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Facebook and Clarity and others), adding 1.1 MB and 732 ms of main-thread time.

  • Reduce unused CSS

    450 ms · 111 KiB

    About 111 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.

  • Google Tag Manager adds 424 ms

    424 ms

    Google Tag Manager costs a phone 424 ms of main-thread work and 812 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: 3.7 s

    A phone's processor spends 3.7 s on main-thread work while loading, 2.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • 2,397 HTML elements

    The page has 2,397 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Legacy JavaScript

    150 ms · 23 KiB

    Polyfills for old browsers add 23 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

  • 12 long tasks on the main thread

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

  • Font display

    50 ms

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

1 checks passed
  • Server response: 263 ms

    263 ms

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

Core Web Vitals

9 to fix67
  • 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.

  • Real-user LCP: 4.2 s

    4.2 s

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

  • Largest Contentful Paint: 14.8 s

    14.8 s

    Your 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 “Camel logo”.

  • Speed Index: 34.0 s

    34.0 s

    Visually, the page fills in at 34.0 s (Speed Index). Good is under 3.4 s.

  • Time to Interactive: 25.0 s

    25.0 s

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

  • Real-user FCP: 2.7 s

    2.7 s

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

  • Real-user TTFB: 992 ms

    992 ms

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

  • First Contentful Paint: 2.3 s

    2.3 s

    The first text or image appears after 2.3 s on a phone. Good is under 1.8 s.

  • Total Blocking Time: 245 ms

    245 ms

    Scripts block taps and scrolling for 245 ms in total while the page loads. Good is under 200 ms.

  • Tap response (INP) got 13% slower for real visitors

    +13%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 168 ms to 193 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

4 checks passed
  • Real-user INP: 193 ms

    193 ms

    Real visitors wait 193 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.

  • Largest content (LCP) got 23% faster for real visitors

    -23%

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

  • Cumulative Layout Shift: 0.001

    0.001

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

Images and page weight

5 to fix18
  • Page weight: 8.7 MB in 99 requests

    8.7 MB

    Your homepage downloads 8.7 MB in 99 requests on a phone: images 7.1 MB (59), scripts 1.2 MB (17) and fonts 179 KiB (3). Under 2 MB keeps phones on slow connections fast.

  • 2 images over 500 KB

    2 images weigh 1.4 MB together. On a phone connection a single image that size takes seconds.

  • 12 images far larger than shown

    1.0 MB

    12 images are downloaded at several times the size a phone draws them, for example mobile.jpg at 1,269 px wide, shown at 350 px. Resized copies would save about 1.0 MB.

  • 17 images in older formats

    17 images (4.1 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.

  • 12 images below the first screen load straight away

    12 images further down the page (1.2 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 2.5 g of CO₂ per visit

    2.46 g

    By the Sustainable Web Design model, a visit to your homepage emits about 2.46 g of CO₂e: 294.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Accessibility

5 to fixGoogle 8793
  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

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

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

  • 4 form fields without a label

    4 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • Alternative text of images should not be repeated as text (2 elements)

    Alternative text of images should not be repeated as text: 2 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

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

1 checks passed
  • 39 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: 39 passed and 5 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

Google 92100
  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

  • 490 internal links, 5 external

    The homepage links to 490 pages on kokuyocamlin.com and 5 external pages.

8 checks passed
  • Meta description: 153 characters

    Your meta description is 153 characters: “Kokuyo Camlin is one of India's oldest art & stationery supplies companies. Explore Camel painting and drawing products…”.

  • One H1 headline

    Your main headline reads: “Indulge in the realm of art with Camel art products”.

  • Title: 65 characters

    Your title is a healthy 65 characters: “Kokuyo Camlin | Camel Art Supplies for Artists, Hobbyists, & Kids”.

  • Canonical URL set

    The canonical URL is https://www.kokuyocamlin.com/camel/.

  • Structured data in place

    Structured data found: FAQPage, 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://www.kokuyocamlin.com/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://www.kokuyocamlin.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.

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: 5 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.

  • Text is in the HTML

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

Other pages

2 to fix70
  • 1 linked page is broken

    Your homepage links to https://www.kokuyocamlin.com/camel/paints/acrylic-colours/individual-bottles-in-metallic-powders, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 1 page without an H1

    https://www.kokuyocamlin.com/camel/store-locator has no <h1> headline, so visitors and search engines get no clear main topic.

  • 7 pages slow to respond

    https://www.kokuyocamlin.com/camel/paints/acrylic-colours/assorted-packs/assorted-pack-of-6-shades-in-10-ml-fluorescent-range, https://www.kokuyocamlin.com/camel/paints/acrylic-colours/individual-bottles, https://www.kokuyocamlin.com/camel/drawing-materials, https://www.kokuyocamlin.com/camel/drawing-materials/acrylic-markers/assorted-pack/assorted-pack-of-acrylic-brush-markers-12-shades, https://www.kokuyocamlin.com/camel/drawing-materials/acrylic-markers/assorted-pack/assorted-pack-of-acrylic-markers-3mm-12-shades and https://www.kokuyocamlin.com/camel/drawing-materials/acrylic-markers/assorted-pack/assorted-pack-of-12-shades and 1 other took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 72 found) and read each the way a search engine does.

5 checks passed
  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 10 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 10 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'getRegistrations')”.

2 checks passed
  • Tap targets are thumb-sized

    25 of 29 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix92
  • 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,471 words of copy

    The homepage carries about 1,471 words of visible text.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Sign up” and “Shop now”.

  • 19 calls to action

    The homepage has 19 calls to action, for example “Join our Community”, “Sign up” and “Colouring Book Kit”.

  • 2 short forms

    2 short forms (2 fields at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 13 testimonial or review blocks and 1 trust badge.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics, Meta Pixel, Microsoft Clarity and Cloudflare Web Analytics.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel 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.

  • 8 cookies set on arrival

    8

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

  • 13 other companies contacted

    Loading the homepage contacts 13 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 kokuyocamlin.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Analytics
Google Analytics | Google Tag Manager | Microsoft Clarity
Hosting
Cloudflare

Company

Founded
1931
Headquarters
Mumbai

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 34 issues on kokuyocamlin.com, including 19 speed issues and 1 conversion gap. 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