Website review, no card needed

aasmabuilders.com logo

aasmabuilders.com website review

Visit site (opens in a new tab)Reviewed 17 November 202637 issues · 75 checks

This review found 37 issues worth fixing on aasmabuilders.com, 17 of them high impact, across 75 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 aasmabuilders.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. aasmabuilders.com at 2.5 s2.5 s
  2. aasmabuilders.com at 4.9 s4.9 s
  3. aasmabuilders.com at 7.4 s7.4 s
  4. aasmabuilders.com at 9.9 s9.9 s
  5. aasmabuilders.com at 12.3 s12.3 s
  6. aasmabuilders.com at 14.8 s14.8 s
  7. aasmabuilders.com at 17.3 s17.3 s
  8. aasmabuilders.com at 19.7 s19.7 s

Speed

9 to fix81
  • Use efficient cache lifetimes

    1.6 s · 4.0 MB

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

  • Render-blocking requests

    4.8 s

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

  • Improve image delivery

    1.1 s · 2.6 MB

    6 images could be 2.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.1 s faster on a phone.

  • Font display

    3.0 s

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

  • YouTube adds 1.3 s

    1.3 s

    YouTube costs a phone 1.3 s of main-thread work and 3.9 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Main-thread work: 6.0 s

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

  • Reduce unused JavaScript

    2.2 MB

    About 2.2 MB of JavaScript is downloaded but never used on this page.

  • 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 4.3 MB and 1.3 s of main-thread time.

  • Mobile performance score: 81

    81/100

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

  • Reduce unused CSS

    150 ms · 159 KiB

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

  • 12 long tasks on the main thread

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

  • Minify JavaScript

    12 KiB

    12 KiB could be saved by minifying JavaScript.

  • Minify CSS

    7 KiB

    7 KiB could be saved by minifying CSS.

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

    261 ms

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

Core Web Vitals

6 to fix92
  • Speed Index: 28.8 s

    28.8 s

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

  • Time to Interactive: 39.2 s

    39.2 s

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

  • First Contentful Paint: 2.3 s

    2.3 s

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

  • Largest Contentful Paint: 2.6 s

    2.6 s

    Your largest element takes 2.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image. Most of its time is resource load delay (7.8 s).

  • Total Blocking Time: 214 ms

    214 ms

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

  • 6 images without width and height

    6 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

    0

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

Images and page weight

1 to fix70
  • Page weight: 8.4 MB in 173 requests

    8.4 MB

    Your homepage downloads 8.4 MB in 173 requests on a phone: scripts 3.9 MB (62), images 3.4 MB (17) and stylesheets 395 KiB (57). Under 2 MB keeps phones on slow connections fast.

  • 1 image below the first screen load straight away

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

  • About 2.4 g of CO₂ per visit

    2.37 g

    By the Sustainable Web Design model, a visit to your homepage emits about 2.37 g of CO₂e: 284.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

5 to fixGoogle 9091
  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Links must have discernible text (1 element)

    Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

  • 2 images without alt text

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

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • The skip-link target should exist and be focusable (1 element)

    The skip-link target should exist and be focusable: 1 element on the page fails this check, rated moderate by axe-core.

  • Headings skip levels

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

1 checks passed
  • 42 automated accessibility rules passed

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

SEO

8 to fixGoogle 5438
  • 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://www.aasmabuilders.com/sitemap.xml, so Google discovers your pages only by following links.

  • No robots.txt

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

  • No X (Twitter) card tag

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

  • 13 internal links, 2 external

    The homepage links to 13 pages on aasmabuilders.com and 2 external pages.

2 checks passed
  • Title: 48 characters

    Your title is a healthy 48 characters: “Aasma Builders & Colonisers Ltd. – Aasma Builder”.

  • Canonical URL set

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

AI search readiness

1 to fix81
  • 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
  • Text is in the HTML

    Your server sends the page's text in the HTML (470 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix88
  • 8 linked pages hidden from search

    https://www.aasmabuilders.com/about-us, https://www.aasmabuilders.com/the-building, https://www.aasmabuilders.com/gallery-3, https://www.aasmabuilders.com/projects-pics, https://www.aasmabuilders.com/project-videos and https://www.aasmabuilders.com/testimonials and 2 others are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 8 pages without a meta description

    https://www.aasmabuilders.com/about-us, https://www.aasmabuilders.com/the-building, https://www.aasmabuilders.com/gallery-3, https://www.aasmabuilders.com/projects-pics, https://www.aasmabuilders.com/project-videos and https://www.aasmabuilders.com/testimonials and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 8 pages slow to respond

    https://www.aasmabuilders.com/about-us, https://www.aasmabuilders.com/the-building, https://www.aasmabuilders.com/gallery-3, https://www.aasmabuilders.com/projects-pics, https://www.aasmabuilders.com/project-videos and https://www.aasmabuilders.com/testimonials and 2 others took over 3 s to send their HTML from our server.

  • 8 internal pages checked

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

5 checks passed
  • Linked pages load

    All 8 pages we checked loaded without an error.

  • 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 an H1

    Each page we checked has a main headline.

  • Every page has a title

    All 8 pages that loaded have a <title>.

Best practices

2 to fixGoogle 7389
  • 5 third-party cookies

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

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Access to font at 'https://ikspl.com/wp-content/uploads/elementor/google-fonts/fonts/roboto-fb5169d9.woff2' from origin…”.

  • Browser-reported issues

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix63
  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

    The homepage carries about 377 words of visible text.

2 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “WhatsApp Contact”.

  • 1 call to action

    The homepage has 1 call to action, for example “Contact”.

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.

  • 1 cookie set on arrival

    1

    Opening the homepage sets 1 cookie, 1 of them by other companies (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.

  • 10 other companies contacted

    Loading the homepage contacts 10 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 aasmabuilders.com, 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
Hosting
Serverwala Cloud Datacenters Private Limited

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 aasmabuilders.com, including 15 speed issues, 8 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