Website review, no card needed

ngkntk.in logo

ngkntk.in website review

Visit site (opens in a new tab)Reviewed 1 November 202628 issues · 58 checks

This review found 28 issues worth fixing on ngkntk.in, 11 of them high impact, across 58 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
6.6 s3.3 sMay 9Oct 243.7 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20264.2 s
May 16, 20264.1 s
May 23, 20265.2 s
May 30, 20266.1 s
Jun 6, 20266.2 s
Jun 13, 20266.2 s
Jun 20, 20265.1 s
Jun 27, 20264.5 s
Jul 4, 20264.6 s
Jul 11, 20264.4 s
Jul 18, 20264.1 s
Jul 25, 20263.7 s
Aug 1, 20263.8 s
Aug 8, 20263.8 s
Aug 15, 20263.8 s
Aug 22, 20263.7 s
Aug 29, 20263.7 s
Sep 5, 20263.7 s
Sep 12, 20263.8 s
Sep 19, 20263.8 s
Sep 26, 20263.7 s
Oct 3, 20263.8 s
Oct 10, 20263.8 s
Oct 17, 20263.8 s
Oct 24, 20263.7 s
Real-visitor tap response (INP)75th percentile, phones
125 ms81 msMay 9Oct 2486 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 202696 ms
May 16, 202695 ms
May 23, 2026109 ms
May 30, 2026118 ms
Jun 6, 2026119 ms
Jun 13, 2026120 ms
Jun 20, 2026106 ms
Jun 27, 202699 ms
Jul 4, 202699 ms
Jul 11, 202697 ms
Jul 18, 202693 ms
Jul 25, 202688 ms
Aug 1, 202689 ms
Aug 8, 202690 ms
Aug 15, 202690 ms
Aug 22, 202689 ms
Aug 29, 202689 ms
Sep 5, 202688 ms
Sep 12, 202690 ms
Sep 19, 202690 ms
Sep 26, 202689 ms
Oct 3, 202689 ms
Oct 10, 202688 ms
Oct 17, 202688 ms
Oct 24, 202686 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 ngkntk.in (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. ngkntk.in at 0.9 s0.9 s
  2. ngkntk.in at 1.8 s1.8 s
  3. ngkntk.in at 2.7 s2.7 s
  4. ngkntk.in at 3.6 s3.6 s
  5. ngkntk.in at 4.5 s4.5 s
  6. ngkntk.in at 5.4 s5.4 s
  7. ngkntk.in at 6.3 s6.3 s
  8. ngkntk.in at 7.2 s7.2 s

Speed

6 to fix74
  • Render-blocking requests

    5.6 s

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

  • Use efficient cache lifetimes

    3.8 s · 618 KiB

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

  • Mobile performance score: 74

    74/100

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

  • Minify JavaScript

    700 ms · 142 KiB

    142 KiB could be saved by minifying JavaScript.

  • Reduce unused JavaScript

    700 ms · 135 KiB

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

  • Reduce unused CSS

    333 KiB

    About 333 KiB of CSS is downloaded but never applied on this page.

  • Document request latency

    8 KiB

    The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

  • 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 third-party service on the page

    1 third-party service load with your homepage (bunny.net), adding 38 KiB and 0 ms of main-thread time.

  • Minify CSS

    4 KiB

    4 KiB could be saved by minifying CSS.

2 checks passed
  • Server response: 270 ms

    270 ms

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

  • Main-thread work: 0.2 s

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

Core Web Vitals

7 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.8 s

    4.8 s

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

  • Real-user FCP: 3.8 s

    3.8 s

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

  • Real-user TTFB: 2.7 s

    2.7 s

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

  • Speed Index: 11.3 s

    11.3 s

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

  • First Contentful Paint: 3.6 s

    3.6 s

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

  • Largest Contentful Paint: 3.6 s

    3.6 s

    Your largest element takes 3.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “This website will be unavailable during maintenance. We wil…”. Most of its time is element render delay (5.7 s).

  • Tap response (INP) held steady for real visitors

    -9%

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

6 checks passed
  • Real-user INP: 98 ms

    98 ms

    Real visitors wait 98 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 10% faster for real visitors

    -10%

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

  • Time to Interactive: 3.6 s

    3.6 s

    The page is fully interactive after 3.6 s.

  • Cumulative Layout Shift: 0.02

    0.02

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

  • Total Blocking Time: 0 ms

    0 ms

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

Images and page weight

100
  • About 0.2 g of CO₂ per visit

    0.18 g

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

1 checks passed
  • Page weight: 668 KiB in 8 requests

    668 KiB

    Your homepage downloads 668 KiB in 8 requests on a phone: stylesheets 337 KiB (3), scripts 281 KiB (2) and fonts 38 KiB (2). That is a lean page.

Accessibility

3 to fixGoogle 8491
  • 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.

  • Zoom is disabled

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

  • Headings should not be empty (1 element)

    Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

1 checks passed
  • 13 automated accessibility rules passed

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

SEO

5 to fixGoogle 9180
  • Title is short (28 characters)

    Your title is only 28 characters: “Emergency Maintenance Notice”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • No social preview image

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

  • Only 0 internal links

    The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.

  • No X (Twitter) card tag

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

4 checks passed
  • Meta description: 95 characters

    Your meta description is 95 characters: “We are doing some work on our site. Please come back later. We'll be up and running in no time.”.

  • One H1 headline

    Your main headline reads: “Emergency Maintenance Notice”.

  • 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.ngkntk.in/sitemap.xml.

AI search readiness

1 to fix83
  • No Organization structured data

    There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

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.

  • llms.txt published

    The site publishes https://www.ngkntk.in/llms.txt (41 KiB, 130 links, though it should open with a “# Title” line), a plain-text guide to the site for AI tools.

Best practices

Google 100100
2 checks passed
  • No console errors

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

6 to fix25
  • 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 calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

  • No social proof

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

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

  • Only about 55 words

    The homepage has only about 55 words of visible text; thin pages give Google and first-time buyers little to go on.

  • No form on the homepage

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

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

Privacy and tracking

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

  • 1 other company contacted

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

Upkeep, stack and company

Stack

CMS
WordPress
Framework
jQuery
Hosting
- CtrlS

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 28 issues on ngkntk.in, including 13 speed issues, 5 SEO issues and 6 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