Website review, no card needed

great-white.in logo

great-white.in website review

Visit site (opens in a new tab)Reviewed 26 October 202648 issues · 89 checks

This review found 48 issues worth fixing on great-white.in, 20 of them high impact, across 89 checks. The most urgent: reduce unused JavaScript. 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
2.5 s1.9 sMay 9Oct 242.2 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.5 s
May 16, 20262.4 s
May 23, 20262.5 s
May 30, 20262.5 s
Jun 6, 20262.5 s
Jun 13, 20262.4 s
Jun 20, 20262.4 s
Jun 27, 20262.3 s
Jul 4, 20262.3 s
Jul 11, 20262.3 s
Jul 18, 20262.2 s
Jul 25, 20262.2 s
Aug 1, 20262.2 s
Aug 8, 20262.1 s
Aug 15, 20262.1 s
Aug 22, 20262.0 s
Aug 29, 20262.0 s
Sep 5, 20262.0 s
Sep 12, 20262.0 s
Sep 19, 20262.0 s
Sep 26, 20262.1 s
Oct 3, 20262.1 s
Oct 10, 20262.1 s
Oct 17, 20262.2 s
Oct 24, 20262.2 s
Real-visitor tap response (INP)75th percentile, phones
97 ms88 msMay 9Oct 2494 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 202695 ms
May 16, 202693 ms
May 23, 202695 ms
May 30, 202695 ms
Jun 6, 202695 ms
Jun 13, 202695 ms
Jun 20, 202694 ms
Jun 27, 202695 ms
Jul 4, 202695 ms
Jul 11, 202696 ms
Jul 18, 202696 ms
Jul 25, 202694 ms
Aug 1, 202690 ms
Aug 8, 202689 ms
Aug 15, 202690 ms
Aug 22, 202692 ms
Aug 29, 202692 ms
Sep 5, 202692 ms
Sep 12, 202692 ms
Sep 19, 202693 ms
Sep 26, 202693 ms
Oct 3, 202693 ms
Oct 10, 202694 ms
Oct 17, 202694 ms
Oct 24, 202694 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 great-white.in (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. great-white.in at 0.8 s0.8 s
  2. great-white.in at 1.6 s1.6 s
  3. great-white.in at 2.4 s2.4 s
  4. great-white.in at 3.2 s3.2 s
  5. great-white.in at 3.9 s3.9 s
  6. great-white.in at 4.7 s4.7 s
  7. great-white.in at 5.5 s5.5 s
  8. great-white.in at 6.3 s6.3 s

Speed

11 to fix20
  • Reduce unused JavaScript

    10.8 s · 2.0 MB

    About 2.0 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 10.8 s faster on a phone.

  • Use efficient cache lifetimes

    4.8 s · 5.1 MB

    59 files are served with short cache lifetimes, so returning visitors download them again (5.1 MB).

  • Render-blocking requests

    3.0 s

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

  • YouTube adds 1.3 s

    1.3 s

    YouTube costs a phone 1.3 s of main-thread work and 3.8 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Font display

    1.6 s

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 1.6 s).

  • Mobile performance score: 20

    20/100

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

  • Improve image delivery

    2.9 MB

    17 images could be 2.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 8 third-party services on the page

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

  • Reduce unused CSS

    600 ms · 130 KiB

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

  • Google Tag Manager adds 356 ms

    356 ms

    Google Tag Manager costs a phone 356 ms of main-thread work and 602 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.8 s

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

  • 20 long tasks on the main thread

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

  • Minify CSS

    150 ms · 18 KiB

    18 KiB could be saved by minifying CSS.

  • Minify JavaScript

    150 ms · 14 KiB

    14 KiB could be saved by minifying JavaScript.

  • Legacy JavaScript

    50 ms · 19 KiB

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

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

1 checks passed
  • Server response: 266 ms

    266 ms

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

Core Web Vitals

12 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 CLS: 0.56

    0.56

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

  • Largest Contentful Paint: 30.3 s

    30.3 s

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

  • Speed Index: 15.6 s

    15.6 s

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

  • Time to Interactive: 43.2 s

    43.2 s

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

  • Cumulative Layout Shift: 0.54

    0.54

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

  • Total Blocking Time: 717 ms

    717 ms

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

  • First Contentful Paint: 3.2 s

    3.2 s

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

  • Real-user LCP: 3.3 s

    3.3 s

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

  • Real-user FCP: 1.9 s

    1.9 s

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

  • Real-user TTFB: 1.1 s

    1.1 s

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

  • 19 images without width and height

    19 images have no width and height attributes, so the layout jumps as each one loads.

  • Tap response (INP) held steady for real visitors

    0%

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

2 checks passed
  • Real-user INP: 107 ms

    107 ms

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

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

    -11%

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

Images and page weight

5 to fix28
  • Page weight: 9.8 MB in 134 requests

    9.8 MB

    Your homepage downloads 9.8 MB in 134 requests on a phone: images 4.5 MB (32), scripts 4.4 MB (40) and fonts 373 KiB (9). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    home-p-cat-wire.png weighs 1.1 MB. On a phone connection a single image that size takes seconds.

  • 25 images in older formats

    25 images (4.5 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.

  • 20 images below the first screen load straight away

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

  • 1 image far larger than shown

    426 KiB

    1 image is downloaded at several times the size a phone draws it, for example home-p-cat-wire.png at 1,000 px wide, shown at 266 px. Resized copies would save about 426 KiB.

  • About 2.8 g of CO₂ per visit

    2.79 g

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

Accessibility

8 to fixGoogle 7688
  • 2 buttons without a name

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

  • <html> element must have a lang attribute (1 element)

    <html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

  • 15 images without alt text

    15 images have no alt text, which hurts accessibility and image search.

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

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • 13 links without text

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

  • 9 form fields without a label

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

  • No page language

    The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

  • Headings skip levels

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

1 checks passed
  • 38 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 45 WCAG 2.2 A/AA and best-practice rules on the phone render: 38 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

7 to fixGoogle 7573
  • Title is long (67 characters)

    Your title is 67 characters, so Google will cut it off around 60: “GreatWhite: Premium Electrical Switches & Home Automation Solutions”.

  • 2 H1 headlines

    There are 2 <h1> headlines (“WE LIVE IN THE WORLD OF POSSIBILITIES” and “Latest Blog”). One clear main headline is easier for people and search engines.

  • Meta description is long (185 characters)

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

  • Structured data has 1 problem

    Structured data found (Organization and WebPage) but with 1 problem, for example “Organization: missing name”.

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 5 links with vague text

    5 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 3 links crawlers can't follow

    3 links have no real href, so search engines can't follow them.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 118 internal links, 5 external

    The homepage links to 118 pages on great-white.in and 5 external pages.

3 checks passed
  • Canonical URL set

    The canonical URL is https://great-white.in/.

  • 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://great-white.in/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://great-white.in/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: 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 (1,293 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix95
  • 1 page without a meta description

    https://great-white.in/arcus-q has no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

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

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

  • 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 15 pages that loaded have a <title>.

Best practices

1 to fixGoogle 7797
  • 5 third-party cookies

    5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • Browser-reported issues

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

3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix75
  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • A 8-field form

    Your longest form asks for 8 fields (6 required). Every extra field lowers completion.

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

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

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “CONTACT US”.

  • 3 calls to action

    The homepage has 3 calls to action, for example “Contact Us”.

  • Analytics in place

    Analytics detected: Google Analytics and Meta Pixel.

  • Direct contact links

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

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and 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, 1 of them by other companies (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.

  • 15 other companies contacted

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

Upkeep, stack and company

Stack

Framework
jQuery
Analytics
Google Analytics

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 48 issues on great-white.in, including 23 speed issues, 7 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

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