Website review, no card needed
meghna-executive.com website review
Visit site (opens in a new tab)Reviewed 3 November 202633 issues · 83 checks
This review found 33 issues worth fixing on meghna-executive.com, 10 of them high impact, across 83 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
74CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 4.0 s |
| May 23, 2026 | 3.8 s |
| May 30, 2026 | 3.6 s |
| Jun 6, 2026 | 3.6 s |
| Jun 13, 2026 | 3.6 s |
| Jun 20, 2026 | 3.6 s |
| Jun 27, 2026 | 3.5 s |
| Jul 4, 2026 | 3.5 s |
| Jul 11, 2026 | 3.6 s |
| Jul 18, 2026 | 3.6 s |
| Jul 25, 2026 | 3.7 s |
| Aug 1, 2026 | 3.6 s |
| Aug 8, 2026 | 3.6 s |
| Aug 15, 2026 | 3.5 s |
| Aug 22, 2026 | 3.4 s |
| Aug 29, 2026 | 3.4 s |
| Sep 5, 2026 | 3.3 s |
| Sep 12, 2026 | 3.3 s |
| Sep 19, 2026 | 3.4 s |
| Sep 26, 2026 | 3.3 s |
| Oct 3, 2026 | 3.4 s |
| Oct 10, 2026 | 3.3 s |
| Oct 17, 2026 | 3.3 s |
| Oct 24, 2026 | 3.5 s |
| Oct 31, 2026 | 3.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 130 ms |
| May 23, 2026 | 119 ms |
| May 30, 2026 | 120 ms |
| Jun 6, 2026 | 110 ms |
| Jun 13, 2026 | 118 ms |
| Jun 20, 2026 | 134 ms |
| Jun 27, 2026 | 133 ms |
| Jul 4, 2026 | 126 ms |
| Jul 11, 2026 | 127 ms |
| Jul 18, 2026 | 130 ms |
| Jul 25, 2026 | 138 ms |
| Aug 1, 2026 | 137 ms |
| Aug 8, 2026 | 132 ms |
| Aug 15, 2026 | 124 ms |
| Aug 22, 2026 | 121 ms |
| Aug 29, 2026 | 123 ms |
| Sep 5, 2026 | 124 ms |
| Sep 12, 2026 | 127 ms |
| Sep 19, 2026 | 118 ms |
| Sep 26, 2026 | 135 ms |
| Oct 3, 2026 | 127 ms |
| Oct 10, 2026 | 136 ms |
| Oct 17, 2026 | 143 ms |
| Oct 24, 2026 | 143 ms |
| Oct 31, 2026 | 151 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
How it loaded on a phone
0.6 s
1.2 s
1.8 s
2.4 s
3.0 s
3.6 s
4.2 s
4.8 s
Speed
Render-blocking requests
1.1 s3 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.
Mobile performance score: 68
68/100Your mobile performance score is 68. Pages that score under 90 lose visitors before the first paint.
Document request latency
600 msThe HTML itself could arrive about 600 ms sooner: redirects, a slow server response or missing compression delay everything after it.
Reduce initial server response time
597 msReduce initial server response time. Google estimates savings of 597 ms on a phone.
Reduce unused JavaScript
300 ms · 56 KiBAbout 56 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.
Server response: 697 ms
697 msYour server takes 697 ms to send the HTML. Google recommends under 600 ms; everything else waits for it.
Improve image delivery
180 KiB4 images could be 180 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
1 long task on the main thread
1 long task block the main thread while loading, the longest for 166 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
129 KiB13 files are served with short cache lifetimes, so returning visitors download them again (129 KiB).
Reduce unused CSS
35 KiBAbout 35 KiB of CSS is downloaded but never applied on this page.
Legacy JavaScript
11 KiBPolyfills 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.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
Minify CSS
2 KiB2 KiB could be saved by minifying CSS.
1 checks passed
Main-thread work: 1.6 s
A phone's processor spends 1.6 s on main-thread work while loading, 669 ms of it running JavaScript. That is comfortably low.
Core Web Vitals
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: 6.9 s
6.9 sYour largest element takes 6.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Executive Motors Ltd.”. Most of its time is element render delay (3.3 s).
Speed Index: 6.7 s
6.7 sVisually, the page fills in at 6.7 s (Speed Index). Good is under 3.4 s.
Real-user LCP: 3.2 s
3.2 sReal visitors wait 3.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 2.5 s
2.5 sReal visitors see the first content after 2.5 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.6 s
1.6 sReal visitors wait 1.6 s for your server to start answering (75th percentile). Good is under 800 ms.
Time to Interactive: 7.0 s
7.0 sThe page becomes fully interactive after 7.0 s. Good is under 3.8 s.
First Contentful Paint: 2.1 s
2.1 sThe first text or image appears after 2.1 s on a phone. Good is under 1.8 s.
17 images without width and height
17 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 18% slower for real visitors
+18%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 130 ms to 151 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user INP: 149 ms
149 msReal visitors wait 149 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.07
0.07For real visitors the layout shifts by 0.07 (75th percentile). Good is under 0.1.
Largest content (LCP) got 14% faster for real visitors
-14%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 4.0 s to 3.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.059
0.059The layout barely moves while loading (CLS 0.059, good is under 0.1).
Total Blocking Time: 58 ms
58 msScripts block the page for only 58 ms while loading. Good is under 200 ms.
Images and page weight
2 images below the first screen load straight away
2 images further down the page (65 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 0.5 g of CO₂ per visit
0.46 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.46 g of CO₂e: 55.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Page weight: 1.6 MB in 71 requests
1.6 MBYour homepage downloads 1.6 MB in 71 requests on a phone: images 611 KiB (27), scripts 484 KiB (21) and HTML 231 KiB (1). That is a lean page.
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
All page content should be contained by landmarks (11 elements)
All page content should be contained by landmarks: 11 elements on the page fail this check, rated moderate by axe-core.
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 (h2 → h4, h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 24 images in the HTML carry an alt attribute.
32 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 35 WCAG 2.2 A/AA and best-practice rules on the phone render: 32 passed and 3 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
robots.txt blocks all crawlers
Your robots.txt disallows the whole site for every crawler, so search engines are told to stay out.
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Blocked from indexing
Google's crawler is blocked from indexing this page.
Title is short (25 characters)
Your title is only 25 characters: “Meghna Executive Holdings”. 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.
22 internal links, 6 external
The homepage links to 22 pages on meghna-executive.com and 6 external pages.
4 checks passed
Meta description: 126 characters
Your meta description is 126 characters: “Meghna Executive Holdings has redefined luxury, setting unmatched innovation, quality, and legacy standards across Bang…”.
Canonical URL set
The canonical URL is https://meghna-executive.com/.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
XML sitemap found
Your XML sitemap is reachable at https://meghna-executive.com/sitemap.xml.
AI search readiness
robots.txt blocks 6 AI answer engine crawlers
6 of 6Your robots.txt shuts out ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Claude search (Claude-SearchBot), Claude (Claude-User), Perplexity (PerplexityBot) and Perplexity (Perplexity-User). These fetch pages to answer people's questions and cite the source, so your site can't be quoted or linked in those answers.
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://meghna-executive.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.
Opted out of AI training for 5 crawlers
robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers.
1 checks passed
Text is in the HTML
Your server sends the page's text in the HTML (608 words), so crawlers that don't run JavaScript still read it.
Other pages
5 pages without a meta description
https://meghna-executive.com/units/executive-motors-ltd, https://meghna-executive.com/units/penthouse-livings-limited, https://meghna-executive.com/units/executive-lifestyles-ltd, https://meghna-executive.com/units/executive-machines-ltd and https://meghna-executive.com/media-center/meh%E2%80%99s-approach-to-modern-manufacturing have no meta description, so Google writes the search snippet from whatever text it finds.
5 pages share a meta description
https://meghna-executive.com/units, https://meghna-executive.com/about, https://meghna-executive.com/media-center, https://meghna-executive.com/sustainability and https://meghna-executive.com/csr use the same meta description. A description written for each page earns more clicks.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://meghna-executive.com/media-center/meh%E2%80%99s-approach-to-modern-manufacturing, whose canonical is https://meghna-executive.com/media-center/meh%e2%80%99s-approach-to-modern-manufacturing. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
3 pages without an H1
https://meghna-executive.com/about, https://meghna-executive.com/sustainability and https://meghna-executive.com/csr have no <h1> headline, so visitors and search engines get no clear main topic.
2 pages with very little text
https://meghna-executive.com/units/executive-lifestyles-ltd and https://meghna-executive.com/media-center 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.
4 pages slow to respond
https://meghna-executive.com/units/executive-motors-ltd, https://meghna-executive.com/units/penthouse-livings-limited, https://meghna-executive.com/units/executive-lifestyles-ltd and https://meghna-executive.com/media-center/meh%E2%80%99s-approach-to-modern-manufacturing took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 16 found) and read each the way a search engine does.
4 checks passed
Linked pages load
11 pages of 15 loaded without an error (the rest turned automated requests away).
Titles are unique
Every page we checked has its own title.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 11 pages that loaded have a <title>.
Best practices
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
2 checks passed
Tap targets are thumb-sized
5 of 6 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
Local business without LocalBusiness data
Your homepage shows a map but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
About 355 words of copy
The homepage carries about 355 words of visible text.
4 checks passed
1 call to action
The homepage has 1 call to action, for example “Contact”.
Direct contact links
Visitors can reach you directly: 2 phone links and 1 email link.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
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 meghna-executive.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Hosting
- DigitalOcean
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 meghna-executive.com, including 15 speed issues, 5 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.