Website review, no card needed

beverlygroup.my logo

beverlygroup.my website review

Visit site (opens in a new tab)Reviewed 22 October 202637 issues · 71 checks

This review found 37 issues worth fixing on beverlygroup.my, 19 of them high impact, across 71 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 beverlygroup.my (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. beverlygroup.my at 1.3 s1.3 s
  2. beverlygroup.my at 2.7 s2.7 s
  3. beverlygroup.my at 4.0 s4.0 s
  4. beverlygroup.my at 5.4 s5.4 s
  5. beverlygroup.my at 6.7 s6.7 s
  6. beverlygroup.my at 8.1 s8.1 s
  7. beverlygroup.my at 9.4 s9.4 s
  8. beverlygroup.my at 10.7 s10.7 s

Speed

11 to fix41
  • Use efficient cache lifetimes

    2.5 s · 2.4 MB

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

  • Render-blocking requests

    2.2 s

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

  • Reduce unused CSS

    1.2 s · 394 KiB

    About 394 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.2 s faster on a phone.

  • Mobile performance score: 41

    41/100

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

  • Main-thread work: 4.6 s

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

  • Document request latency

    550 ms · 149 KiB

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

  • Reduce unused JavaScript

    260 ms · 427 KiB

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

  • Reduce initial server response time

    569 ms

    Reduce initial server response time. Google estimates savings of 569 ms on a phone.

  • Google Tag Manager adds 383 ms

    383 ms

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

  • 20 long tasks on the main thread

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

  • Server response: 669 ms

    669 ms

    Your server takes 669 ms to send the HTML. Google recommends under 600 ms; everything else waits for it.

  • 3 third-party services on the page

    3 third-party services load with your homepage (Google Tag Manager, Google Fonts and Google Analytics), adding 202 KiB and 383 ms of main-thread time.

  • Legacy JavaScript

    60 KiB

    Polyfills for old browsers add 60 KiB JavaScript that modern phones do not need.

  • Improve image delivery

    25 KiB

    1 image could be 25 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Minify CSS

    11 KiB

    11 KiB could be saved by minifying CSS.

  • Phones get a much slower page than desktops

    Desktop scores 76 but mobile only 41. A gap that wide usually means heavy scripts and images that hit phones hardest.

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

Core Web Vitals

5 to fix51
  • Speed Index: 16.5 s

    16.5 s

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

  • Time to Interactive: 14.1 s

    14.1 s

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

  • First Contentful Paint: 4.8 s

    4.8 s

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

  • Largest Contentful Paint: 5.4 s

    5.4 s

    Your largest element takes 5.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Beverly Group”.

  • Total Blocking Time: 902 ms

    902 ms

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

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

    0.017

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

Images and page weight

1 to fix85
  • Page weight: 2.8 MB in 60 requests

    2.8 MB

    Your homepage downloads 2.8 MB in 60 requests on a phone: images 1.1 MB (12), scripts 1.1 MB (28) and stylesheets 338 KiB (14). Under 2 MB keeps phones on slow connections fast.

  • 3 images in older formats

    3 images (399 KiB) 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.

  • About 0.8 g of CO₂ per visit

    0.80 g

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

2 checks passed
  • 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

3 to fixGoogle 9093
  • Images must have alternative text (1 element)

    Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.

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

  • 2 tap targets too small

    2 tap targets are too small or too close together to hit reliably with a finger.

1 checks passed
  • 41 automated accessibility rules passed

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

SEO

7 to fixGoogle 5441
  • Page is set to noindex

    The robots meta tag says “noindex, nofollow”: Google is told not to list this page at all.

  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

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

  • No structured data

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

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

  • No XML sitemap

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

  • No X (Twitter) card tag

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

  • 77 internal links, 6 external

    The homepage links to 77 pages on beverlygroup.my and 6 external pages.

3 checks passed
  • Title: 64 characters

    Your title is a healthy 64 characters: “Beverly Group – Malaysia & Singapore High End Property Developer”.

  • Canonical URL set

    The canonical URL is https://beverlygroup.my/.

  • robots.txt in place

    robots.txt is in place.

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.

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

Other pages

4 to fix58
  • 1 linked page is broken

    Your homepage links to https://beverlygroup.my/our-projects/current-projects/altris, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 14 linked pages hidden from search

    https://beverlygroup.my/about-us, https://beverlygroup.my/our-projects/current-projects, https://beverlygroup.my/our-projects/completed-projects, https://beverlygroup.my/upcoming-projects, https://beverlygroup.my/site-progress and https://beverlygroup.my/news-activities and 8 others are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 14 pages without a meta description

    https://beverlygroup.my/about-us, https://beverlygroup.my/our-projects/current-projects, https://beverlygroup.my/our-projects/completed-projects, https://beverlygroup.my/upcoming-projects, https://beverlygroup.my/site-progress and https://beverlygroup.my/news-activities and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://beverlygroup.my/contact has no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page slow to respond

    https://beverlygroup.my/about-us took over 3 s to send its 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.

3 checks passed
  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has a title

    All 14 pages that loaded have a <title>.

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

4 to fix58
  • 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: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

  • 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 57 words

    The homepage has only about 57 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.

2 checks passed
  • 14 calls to action

    The homepage has 14 calls to action, for example “Join Us”, “Contact Us” and “Schedule A Visit”.

  • Analytics in place

    Analytics detected: Google Analytics.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

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

  • 2 cookies set on arrival

    2

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

  • 4 other companies contacted

    Loading the homepage contacts 4 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 beverlygroup.my, 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
Analytics
Google Analytics

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 37 issues on beverlygroup.my, including 16 speed issues, 7 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