Website review, no card needed

hdworks.in logo

hdworks.in website review

Visit site (opens in a new tab)Reviewed 29 October 202633 issues · 70 checks

This review found 33 issues worth fixing on hdworks.in, 9 of them high impact, across 70 checks. The most urgent: use efficient cache lifetimes. 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 hdworks.in (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. hdworks.in at 0.5 s0.5 s
  2. hdworks.in at 0.9 s0.9 s
  3. hdworks.in at 1.4 s1.4 s
  4. hdworks.in at 1.8 s1.8 s
  5. hdworks.in at 2.3 s2.3 s
  6. hdworks.in at 2.7 s2.7 s
  7. hdworks.in at 3.2 s3.2 s
  8. hdworks.in at 3.6 s3.6 s

Speed

7 to fix82
  • Use efficient cache lifetimes

    1.3 s · 982 KiB

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

  • Mobile performance score: 82

    82/100

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

  • 4 third-party services on the page

    4 third-party services load with your homepage (YouTube, Other Google APIs/SDKs and Google/Doubleclick Ads and others), adding 1.0 MB and 559 ms of main-thread time.

  • YouTube adds 549 ms

    549 ms

    YouTube costs a phone 549 ms of main-thread work and 995 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.

  • Reduce unused JavaScript

    516 KiB

    About 516 KiB of JavaScript is downloaded but never used on this page.

  • Render-blocking requests

    500 ms

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

  • Improve image delivery

    352 KiB

    7 images could be 352 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 4 long tasks on the main thread

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

  • Reduce unused CSS

    111 KiB

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

  • Legacy JavaScript

    11 KiB

    Polyfills for old browsers add 11 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.

2 checks passed
  • Main-thread work: 1.7 s

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

  • Server response: 2 ms

    2 ms

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

Core Web Vitals

4 to fix85
  • Time to Interactive: 12.3 s

    12.3 s

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

  • Speed Index: 6.2 s

    6.2 s

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

  • Cumulative Layout Shift: 0.18

    0.18

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

  • 4 images without width and height

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

3 checks passed
  • Total Blocking Time: 172 ms

    172 ms

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

  • Largest Contentful Paint: 2.2 s

    2.2 s

    Your largest element renders in 2.2 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Head Digital Works operates India's marquee gaming brand 'A…”.

  • First Contentful Paint: 1.1 s

    1.1 s

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

Images and page weight

2 to fix78
  • Page weight: 2.0 MB in 74 requests

    2.0 MB

    Your homepage downloads 2.0 MB in 74 requests on a phone: scripts 1.0 MB (31), images 743 KiB (15) and fonts 82 KiB (2). Under 2 MB keeps phones on slow connections fast.

  • 1 image below the first screen load straight away

    1 image further down the page (394 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 0.6 g of CO₂ per visit

    0.57 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

3 to fixGoogle 8394
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • 3 images without alt text

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

  • 13 links without text

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

  • Headings skip levels

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

1 checks passed
  • 37 automated accessibility rules passed

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

SEO

3 to fixGoogle 9288
  • No structured data

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

  • No XML sitemap

    No XML sitemap at https://hdworks.in/sitemap.xml, so Google discovers your pages only by following links.

  • No robots.txt

    There is no robots.txt at hdworks.in/robots.txt, the first file search crawlers ask for.

  • 19 internal links, 6 external

    The homepage links to 19 pages on hdworks.in and 6 external pages.

5 checks passed
  • Meta description: 108 characters

    Your meta description is 108 characters: “Mobile Gaming Redefined explore more WHO WE ARE We own and operate India's marquee gaming brand 'A23'. We...”.

  • One H1 headline

    Your main headline reads: “Mobile GamingRedefined”.

  • Title: 30 characters

    Your title is a healthy 30 characters: “Head Digital Works - Home page”.

  • Canonical URL set

    The canonical URL is https://hdworks.in/.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

AI search readiness

2 to fix63
  • Most text only appears after JavaScript runs

    24%

    A phone browser shows 620 words, but the HTML your server sends has only 151. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

  • 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://hdworks.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.

1 checks passed
  • AI answer engines may read the site

    There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.

Other pages

7 to fix50
  • 1 page without a title

    https://hdworks.in/blog/how-find-fix-memory-problems-android-app-head-digital-works-pvt has no <title>, so Google invents the link text in results.

  • 6 pages point its canonical at the homepage

    https://hdworks.in/about-us, https://hdworks.in/join-our-team, https://hdworks.in/investors, https://hdworks.in/about-us/corporate-social-responsibility, https://hdworks.in/about-us/our-portfolio and https://hdworks.in/social/blogs declare the homepage as their canonical URL, which tells Google they are copies of the homepage and keeps them out of search results. A site-wide template setting usually causes this.

  • 4 linked pages hidden from search

    https://hdworks.in/about-us/our-story, https://hdworks.in/join-our-team/hdw-culture, https://hdworks.in/contact-us and https://hdworks.in/legal are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 3 pages share a title

    /, https://hdworks.in/investors and https://hdworks.in/social/blogs all use the title “Head Digital Works - Home page”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 2 pages without a meta description

    https://hdworks.in/blog/seo-tech and https://hdworks.in/blog/how-find-fix-memory-problems-android-app-head-digital-works-pvt have no meta description, so Google writes the search snippet from whatever text it finds.

  • 4 pages share a meta description

    https://hdworks.in/investors and https://hdworks.in/social/blogs use the same meta description. A description written for each page earns more clicks.

  • 2 pages without an H1

    https://hdworks.in/blog/seo-tech and https://hdworks.in/blog/how-find-fix-memory-problems-android-app-head-digital-works-pvt have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://hdworks.in/investors has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 12 internal pages checked

    We fetched 12 pages linked from your homepage and read each the way a search engine does.

1 checks passed
  • Linked pages load

    All 12 pages we checked loaded without an error.

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

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix50
  • 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.

  • Thin social proof

    Social proof on the homepage: “80 M+ Users”. Pairing it with named testimonials or customer logos makes it far more convincing.

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

  • About 620 words of copy

    The homepage carries about 620 words of visible text.

1 checks passed
  • 3 calls to action

    The homepage has 3 calls to action, for example “JOIN THE TEAM” and “Contact Us”.

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 hdworks.in, 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 © 2024.

Stack

CMS
WordPress
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 33 issues on hdworks.in, including 11 speed issues, 3 SEO issues and 4 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