Website review, no card needed

merlinprojects.com logo

merlinprojects.com website review

Visit site (opens in a new tab)Reviewed 2 November 202640 issues · 90 checks

This review found 40 issues worth fixing on merlinprojects.com, 11 of them high impact, across 90 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
3.0 s2.2 sMay 16Oct 312.4 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.9 s
May 23, 20262.9 s
May 30, 20262.8 s
Jun 6, 20262.7 s
Jun 13, 20262.8 s
Jun 20, 20262.7 s
Jun 27, 20262.7 s
Jul 4, 20262.7 s
Jul 11, 20262.6 s
Jul 18, 20262.8 s
Jul 25, 20262.7 s
Aug 1, 20262.6 s
Aug 8, 20262.6 s
Aug 15, 20262.4 s
Aug 22, 20262.3 s
Aug 29, 20262.6 s
Sep 5, 20262.7 s
Sep 12, 20262.7 s
Sep 19, 20262.7 s
Sep 26, 20262.4 s
Oct 3, 20262.4 s
Oct 10, 20262.4 s
Oct 17, 20262.4 s
Oct 24, 20262.5 s
Oct 31, 20262.4 s
Real-visitor tap response (INP)75th percentile, phones
200 ms130 msMay 16Oct 31138 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026192 ms
May 23, 2026172 ms
May 30, 2026145 ms
Jun 6, 2026144 ms
Jun 13, 2026152 ms
Jun 20, 2026145 ms
Jun 27, 2026148 ms
Jul 4, 2026145 ms
Jul 11, 2026139 ms
Jul 18, 2026153 ms
Jul 25, 2026154 ms
Aug 1, 2026156 ms
Aug 8, 2026155 ms
Aug 15, 2026144 ms
Aug 22, 2026144 ms
Aug 29, 2026149 ms
Sep 5, 2026155 ms
Sep 12, 2026153 ms
Sep 19, 2026155 ms
Sep 26, 2026146 ms
Oct 3, 2026145 ms
Oct 10, 2026144 ms
Oct 17, 2026142 ms
Oct 24, 2026142 ms
Oct 31, 2026138 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 merlinprojects.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. merlinprojects.com at 1.3 s1.3 s
  2. merlinprojects.com at 2.5 s2.5 s
  3. merlinprojects.com at 3.8 s3.8 s
  4. merlinprojects.com at 5.1 s5.1 s
  5. merlinprojects.com at 6.3 s6.3 s
  6. merlinprojects.com at 7.6 s7.6 s
  7. merlinprojects.com at 8.8 s8.8 s
  8. merlinprojects.com at 10.1 s10.1 s

Speed

11 to fix60
  • Reduce unused JavaScript

    4.9 s · 1.0 MB

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

  • Render-blocking requests

    1.4 s

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

  • Use efficient cache lifetimes

    600 ms · 780 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Google CDN and kenyt.ai and others), adding 2.2 MB and 1.1 s of main-thread time.

  • Mobile performance score: 60

    60/100

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

  • Reduce unused CSS

    450 ms · 114 KiB

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

  • Legacy JavaScript

    450 ms · 51 KiB

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

  • Google Tag Manager adds 414 ms

    414 ms

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

  • Google CDN adds 306 ms

    306 ms

    Google CDN costs a phone 306 ms of main-thread work and 738 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.4 s

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

  • kenyt.ai adds 191 ms

    191 ms

    kenyt.ai costs a phone 191 ms of main-thread work and 577 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.

  • Improve image delivery

    245 KiB

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

  • 16 long tasks on the main thread

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

  • Minify JavaScript

    35 KiB

    35 KiB could be saved by minifying JavaScript.

  • 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: 241 ms

    241 ms

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

Core Web Vitals

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

  • Largest Contentful Paint: 13.8 s

    13.8 s

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

  • Time to Interactive: 22.3 s

    22.3 s

    The page becomes fully interactive after 22.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.

  • Real-user LCP: 3.4 s

    3.4 s

    Real visitors wait 3.4 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.

  • Total Blocking Time: 315 ms

    315 ms

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

  • First Contentful Paint: 2.1 s

    2.1 s

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

  • 2 images without width and height

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

5 checks passed
  • Real-user INP: 138 ms

    138 ms

    Real visitors wait 138 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.

  • Tap response (INP) got 23% faster for real visitors

    -23%

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

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

    -16%

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix70
  • Page weight: 13.1 MB in 137 requests

    13.1 MB

    Your homepage downloads 13.1 MB in 137 requests on a phone: media 8.9 MB (4), scripts 2.3 MB (40) and images 1.1 MB (41). Under 2 MB keeps phones on slow connections fast.

  • About 3.7 g of CO₂ per visit

    3.72 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

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

Accessibility

4 to fix82
  • 4 form fields without a label

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

  • 2 text elements with low contrast

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

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • 1 tap target too small

    1 tap target is too small or too close together to hit reliably with a finger.

  • No main landmark

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

  • Headings skip levels

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

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (2 elements).

1 checks passed
  • Every image has alt text

    All 58 images in the HTML carry an alt attribute.

SEO

3 to fixGoogle 9287
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • 4 links with vague text

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

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

  • 27 internal links, 5 external

    The homepage links to 27 pages on merlinprojects.com and 5 external pages.

7 checks passed
  • Meta description: 142 characters

    Your meta description is 142 characters: “Merlin Group – Leading real estate developer in Kolkata, Pune, Chennai, Ahmedabad & Raipur. Explore premium residential…”.

  • Title: 59 characters

    Your title is a healthy 59 characters: “Real Estate Developer in Kolkata And Pune - Merlin Projects”.

  • Canonical URL set

    The canonical URL is https://www.merlinprojects.com/.

  • Structured data in place

    Structured data found: HomeAndConstructionBusiness, Organization, Person and WebSite.

  • Open Graph tags complete

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

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

AI search readiness

100
  • No llms.txt

    There is no https://www.merlinprojects.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.

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 (417 words), so crawlers that don't run JavaScript still read it.

Other pages

6 to fix38
  • 1 linked page is broken

    Your homepage links to https://www.merlinprojects.com/project, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 1 page without a title

    https://www.merlinprojects.com/blog/f-residences-merlin-is-redefining-luxury-lifestyle-in-kolkata has no <title>, so Google invents the link text in results.

  • 2 pages share a title

    https://www.merlinprojects.com/privacy-policy and https://www.merlinprojects.com/disclaimer all use the title “Merlin”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 4 pages without a meta description

    https://www.merlinprojects.com/blog/f-residences-merlin-is-redefining-luxury-lifestyle-in-kolkata, https://www.merlinprojects.com/blog/the-majesty-of-rise-returns-in-rajarhat, https://www.merlinprojects.com/privacy-policy and https://www.merlinprojects.com/disclaimer have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 links to non-canonical URLs

    Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://www.merlinprojects.com/blog/Bengal-is-finally-rewriting-its-real-estate-playbook., whose canonical is https://www.merlinprojects.com/blog/6-Bengal-is-finally-rewriting-its-real-estate-playbook. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 11 pages without an H1

    https://www.merlinprojects.com/aboutus, https://www.merlinprojects.com/projects, https://www.merlinprojects.com/testimonials, https://www.merlinprojects.com/blog/Bengal-is-finally-rewriting-its-real-estate-playbook., https://www.merlinprojects.com/blog/CREDAI-Seeks-Policy-Reform and https://www.merlinprojects.com/blog/f-residences-merlin-is-redefining-luxury-lifestyle-in-kolkata and 5 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages with very little text

    https://www.merlinprojects.com/projects and https://www.merlinprojects.com/blog have 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
  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

Best practices

2 to fixGoogle 9287
  • 1 small tap target

    1 of 5 tappable elements near the top of the page is smaller than 24 px, hard to hit with a thumb.

  • 3 JavaScript errors while loading

    3 errors were 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”).

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix81
  • 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: 7 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No map or directions link

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

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

    The homepage carries about 408 words of visible text.

6 checks passed
  • 13 calls to action

    The homepage has 13 calls to action, for example “call-button” and “Enquire”.

  • 1 short form

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

  • Analytics in place

    Analytics detected: Cloudflare Web Analytics.

  • Direct contact links

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

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

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

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

  • 7 cookies set on arrival

    7

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

  • 21 other companies contacted

    Loading the homepage contacts 21 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 merlinprojects.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
Hosting
Cloudflare

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 40 issues on merlinprojects.com, including 21 speed issues, 3 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