Website review, no card needed

gkboptical.com logo

gkboptical.com website review

Visit site (opens in a new tab)Reviewed 1 November 202644 issues · 92 checks

This review found 44 issues worth fixing on gkboptical.com, 19 of them high impact, across 92 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
8.3 s1.4 sMay 9Oct 243.2 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.2 s
May 16, 20262.2 s
May 23, 20262.4 s
May 30, 20262.7 s
Jun 6, 20263.0 s
Jun 20, 20263.2 s
Jun 27, 20263.3 s
Jul 4, 20263.4 s
Jul 11, 20266.5 s
Jul 18, 20267.1 s
Jul 25, 20267.5 s
Aug 1, 20267.6 s
Aug 8, 20267.3 s
Aug 15, 20266.7 s
Aug 22, 20265.6 s
Aug 29, 20263.8 s
Sep 5, 20263.2 s
Sep 12, 20263.3 s
Sep 19, 20263.3 s
Sep 26, 20263.4 s
Oct 3, 20263.3 s
Oct 10, 20263.3 s
Oct 17, 20263.3 s
Oct 24, 20263.2 s
Real-visitor tap response (INP)75th percentile, phones
522 ms89 msMay 9Oct 24465 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026139 ms
May 16, 2026142 ms
May 23, 2026150 ms
May 30, 2026161 ms
Jun 6, 2026171 ms
Jun 20, 2026181 ms
Jun 27, 2026202 ms
Jul 4, 2026249 ms
Jul 11, 2026407 ms
Jul 18, 2026419 ms
Jul 25, 2026426 ms
Aug 1, 2026430 ms
Aug 8, 2026425 ms
Aug 15, 2026410 ms
Aug 22, 2026402 ms
Aug 29, 2026392 ms
Sep 5, 2026412 ms
Sep 12, 2026472 ms
Sep 19, 2026462 ms
Sep 26, 2026462 ms
Oct 3, 2026436 ms
Oct 10, 2026398 ms
Oct 17, 2026423 ms
Oct 24, 2026465 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 gkboptical.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. gkboptical.com at 1.1 s1.1 s
  2. gkboptical.com at 2.1 s2.1 s
  3. gkboptical.com at 3.2 s3.2 s
  4. gkboptical.com at 4.2 s4.2 s
  5. gkboptical.com at 5.3 s5.3 s
  6. gkboptical.com at 6.3 s6.3 s
  7. gkboptical.com at 7.4 s7.4 s
  8. gkboptical.com at 8.4 s8.4 s

Speed

11 to fix42
  • Improve image delivery

    10.7 s · 9.6 MB

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

  • Reduce unused JavaScript

    2.9 s · 531 KiB

    About 531 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.9 s faster on a phone.

  • Use efficient cache lifetimes

    1.7 s · 343 KiB

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

  • Render-blocking requests

    1.2 s

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

  • Mobile performance score: 42

    42/100

    Your mobile performance score is 42. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Main-thread work: 4.8 s

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

  • 8 third-party services on the page

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

  • Google Tag Manager adds 704 ms

    704 ms

    Google Tag Manager costs a phone 704 ms of main-thread work and 709 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.

  • 12 long tasks on the main thread

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

  • Facebook adds 246 ms

    246 ms

    Facebook costs a phone 246 ms of main-thread work and 310 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.

  • 2,755 HTML elements

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

  • Legacy JavaScript

    26 KiB

    Polyfills for old browsers add 26 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: 539 ms

    539 ms

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

Core Web Vitals

10 to fix33
  • 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.4 s

    4.4 s

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

  • Real-user INP: 873 ms

    873 ms

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

  • Largest Contentful Paint: 52.1 s

    52.1 s

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

  • Speed Index: 26.6 s

    26.6 s

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

  • Time to Interactive: 54.4 s

    54.4 s

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

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

    +216%

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

  • Largest content (LCP) got 46% slower for real visitors

    +46%

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

  • Total Blocking Time: 563 ms

    563 ms

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

  • Cumulative Layout Shift: 0.179

    0.179

    The layout shifts by 0.179 while loading, so content jumps under the reader's thumb. Good is under 0.1.

4 checks passed
  • Real-user CLS: 0.02

    0.02

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

  • Real-user FCP: 1.6 s

    1.6 s

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

  • Real-user TTFB: 655 ms

    655 ms

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

  • First Contentful Paint: 1.4 s

    1.4 s

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

Images and page weight

4 to fix25
  • Page weight: 19.3 MB in 172 requests

    19.3 MB

    Your homepage downloads 19.3 MB in 172 requests on a phone: images 10.6 MB (49), media 6.5 MB (4) and scripts 1.7 MB (50). Under 2 MB keeps phones on slow connections fast.

  • 8 images far larger than shown

    4.6 MB

    8 images are downloaded at several times the size a phone draws them, for example 2022_07_27_GKB1234-new_copy_428_x_286_1.jpg at 9,160 px wide, shown at 165 px. Resized copies would save about 4.6 MB.

  • 2 images over 500 KB

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

  • 1 image in older formats

    1 image (1.0 MB) is 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 5.5 g of CO₂ per visit

    5.48 g

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

12 to fixGoogle 7084
  • 14 buttons without a name

    14 buttons have no accessible name, so screen readers announce just “button”.

  • Certain ARIA roles must contain particular children (3 elements)

    Certain ARIA roles must contain particular children: 3 elements on the page fail this check, rated critical by axe-core.

  • ARIA attributes must conform to valid values (1 element)

    ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

  • 14 tap targets too small

    14 tap targets are too small or too close together to hit reliably with a finger.

  • 85 form fields without a label

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

  • Document should not have more than one contentinfo landmark (1 element)

    Document should not have more than one contentinfo landmark: 1 element on the page fails 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.

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

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

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

  • 2 links without text

    2 visible links have no text or label, so screen readers cannot say where they go.

  • Headings should not be empty (6 elements)

    Headings should not be empty: 6 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 147 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 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 38 passed and 12 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 10092
  • Meta description is long (186 characters)

    Your meta description is 186 characters; Google truncates after about 160, so the end of your pitch is cut.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 278 internal links, 1 external

    The homepage links to 278 pages on gkboptical.com and 1 external page.

6 checks passed
  • One H1 headline

    Your main headline reads: “GKB Opticals - Sunglasses, Eyeglasses & Contact Lenses Online”.

  • Title: 58 characters

    Your title is a healthy 58 characters: “Buy Eyeglasses, Sunglasses & Contact Lenses - GKB Opticals”.

  • Canonical URL set

    The canonical URL is https://gkboptical.com/.

  • Structured data in place

    Structured data found: LocalBusiness, Optician, Organization and WebSite.

  • 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://gkboptical.com/sitemap.xml.

AI search readiness

1 to fix83
  • Parts of the site are closed to 3 AI crawlers

    Your robots.txt lets ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User) and Perplexity (PerplexityBot) read the homepage but closes other sections to them, so answers about those pages can't cite you.

  • No llms.txt

    There is no https://www.gkboptical.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
  • Organization data: 4 of 6 facts

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

  • Text is in the HTML

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

Other pages

100
  • 15 internal pages checked

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

7 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

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

  • Every page has a meta description

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

Best practices

2 to fixGoogle 7391
  • 1 third-party cookie

    1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

2 checks passed
  • Tap targets are thumb-sized

    50 of 58 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix94
  • Thin social proof

    Social proof on the homepage: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

  • About 339 words of copy

    The homepage carries about 339 words of visible text.

8 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “shop now”.

  • 31 calls to action

    The homepage has 31 calls to action, for example “Book an Eye Test”, “Contact lenses” and “Contact us”.

  • Analytics in place

    Analytics detected: Meta Pixel and Microsoft Clarity.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 0 email links.

  • Opening hours shown

    Your opening hours are on the homepage.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

  • 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

1 to fix
  • 6 trackers load before any consent

    6

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

  • 10 cookies set on arrival

    10

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

  • 23 other companies contacted

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

Upkeep, stack and company

Stack

Framework
Next.js
Analytics
Microsoft Clarity
Hosting
AWS

Company

Founded
1959
Headquarters
Kolkata

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 44 issues on gkboptical.com, including 21 speed issues, 2 SEO 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