Website review, no card needed

puneetkathar.com logo

puneetkathar.com website review

Visit site (opens in a new tab)Reviewed 10 November 202643 issues · 77 checks

This review found 43 issues worth fixing on puneetkathar.com, 15 of them high impact, across 77 checks. The most urgent: 4 images over 500 KB. 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

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

How it loaded on a phone

  1. puneetkathar.com at 0.4 s0.4 s
  2. puneetkathar.com at 0.9 s0.9 s
  3. puneetkathar.com at 1.3 s1.3 s
  4. puneetkathar.com at 1.7 s1.7 s
  5. puneetkathar.com at 2.2 s2.2 s
  6. puneetkathar.com at 2.6 s2.6 s
  7. puneetkathar.com at 3.0 s3.0 s
  8. puneetkathar.com at 3.5 s3.5 s

Speed

8 to fix46
  • Reduce unused JavaScript

    3.8 s · 789 KiB

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

  • Mobile performance score: 46

    46/100

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

  • Main-thread work: 4.7 s

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

  • 7 third-party services on the page

    7 third-party services load with your homepage (YouTube, Google Tag Manager and Google/Doubleclick Ads and others), adding 1.6 MB and 1.0 s of main-thread time.

  • Reduce unused CSS

    750 ms · 174 KiB

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

  • Improve image delivery

    300 ms · 511 KiB

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

  • Render-blocking requests

    750 ms

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

  • YouTube adds 583 ms

    583 ms

    YouTube costs a phone 583 ms of main-thread work and 1,006 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.

  • Font display

    200 ms

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

  • 14 long tasks on the main thread

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

  • Minify CSS

    20 ms · 11 KiB

    11 KiB could be saved by minifying CSS.

  • Use efficient cache lifetimes

    17 KiB

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

  • Legacy JavaScript

    10 KiB

    Polyfills for old browsers add 10 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: 28 ms

    28 ms

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

Core Web Vitals

6 to fix55
  • First Contentful Paint: 8.7 s

    8.7 s

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

  • Largest Contentful Paint: 45.5 s

    45.5 s

    Your largest element takes 45.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “FREELANCE WEB DEVELOPER Hello, I’m Puneet Kathar| Welcome t…”.

  • Time to Interactive: 49.1 s

    49.1 s

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

  • Speed Index: 8.7 s

    8.7 s

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

  • Total Blocking Time: 412 ms

    412 ms

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

  • 27 images without width and height

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

1 checks passed
  • Cumulative Layout Shift: 0.011

    0.011

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

Images and page weight

5 to fix28
  • 4 images over 500 KB

    4 images weigh 64.9 MB together. On a phone connection a single image that size takes seconds.

  • Page weight: 14.5 MB in 94 requests

    14.5 MB

    Your homepage downloads 14.5 MB in 94 requests on a phone: images 12.6 MB (37), scripts 1.5 MB (22) and stylesheets 142 KiB (12). Under 2 MB keeps phones on slow connections fast.

  • 18 images in older formats

    18 images (66.3 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 (66.3 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 1 image far larger than shown

    93 KiB

    1 image is downloaded at several times the size a phone draws it, for example bdsm.png at 1,920 px wide, shown at 366 px. Resized copies would save about 93 KiB.

  • About 4.1 g of CO₂ per visit

    4.10 g

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

Accessibility

12 to fixGoogle 8782
  • Certain ARIA roles must be contained by particular parents (12 elements)

    Certain ARIA roles must be contained by particular parents: 12 elements on the page fail this check, rated critical by axe-core.

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

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

  • 17 text elements with low contrast

    17 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Orphan list items

    Some list items are not inside a list.

  • ARIA progressbar nodes must have an accessible name (4 elements)

    ARIA progressbar nodes must have an accessible name: 4 elements on the page fail this check, rated serious by axe-core.

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

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

    All page content should be contained by landmarks: 24 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.

  • 18 links without text

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

  • 4 form fields without a label

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

  • Elements with role="dialog" or role="alertdialog" do not have accessible names.

    Elements with role="dialog" or role="alertdialog" do not have accessible names. (1 element).

  • 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 (h2 → h6, h2 → h4 and h2 → h6), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 34 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 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 38 passed and 10 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 10082
  • No structured data

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

  • Meta description is short (61 characters)

    Your meta description is only 61 characters: “Offering Web Development services including E-Commerce, SaaS,”. 70 to 160 characters is enough to sell the click.

  • 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 (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • Only 1 internal link

    The homepage links to only 1 page 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
  • One H1 headline

    Your main headline reads: “Hello, I’m Welcome to my Portfolio.”.

  • Title: 33 characters

    Your title is a healthy 33 characters: “Freelance Web Dev | Puneet Kathar”.

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

AI search readiness

1 to fix88
  • 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.

  • No llms.txt

    There is no https://puneetkathar.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
  • 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 (942 words), so crawlers that don't run JavaScript still read it.

Best practices

3 to fixGoogle 6588
  • 5 third-party cookies

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

  • 2 JavaScript errors while loading

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

  • 5 distorted images

    5 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

  • Browser-reported issues

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

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix83
  • 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 640 words of copy

    The homepage carries about 640 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: “Pricing” and “Contact”.

  • 4 calls to action

    The homepage has 4 calls to action, for example “Pricing” and “Contact”.

  • 1 short form

    A short form (4 fields at most) is right on the homepage, asking for an email.

  • Social proof on the page

    Social proof on the homepage: 11 testimonial or review blocks and 8 customer or partner logos.

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

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

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

  • 7 other companies contacted

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

Upkeep, stack and company

  • The footer still says © 2022.

Stack

Framework
Next.js
Hosting
AWS

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 43 issues on puneetkathar.com, including 14 speed issues, 5 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