Website review, no card needed

allenandgledhill.com logo

allenandgledhill.com website review

Visit site (opens in a new tab)Reviewed 19 November 202645 issues · 87 checks

This review found 45 issues worth fixing on allenandgledhill.com, 18 of them high impact, across 87 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
4.0 s2.2 sMay 30Nov 142.4 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20262.9 s
Jun 6, 20262.8 s
Jun 13, 20262.7 s
Jun 20, 20262.7 s
Jun 27, 20262.7 s
Jul 4, 20262.8 s
Jul 11, 20262.9 s
Jul 18, 20263.3 s
Jul 25, 20262.9 s
Aug 1, 20263.1 s
Aug 8, 20263.1 s
Aug 15, 20262.8 s
Aug 22, 20263.5 s
Aug 29, 20263.0 s
Sep 5, 20262.8 s
Sep 12, 20262.7 s
Sep 19, 20262.5 s
Sep 26, 20262.5 s
Oct 3, 20262.7 s
Oct 10, 20263.2 s
Oct 17, 20263.5 s
Oct 24, 20263.8 s
Oct 31, 20263.4 s
Nov 7, 20262.5 s
Nov 14, 20262.4 s
Real-visitor tap response (INP)75th percentile, phones
113 ms68 msMay 30Nov 1473 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 202689 ms
Jun 6, 202692 ms
Jun 13, 2026103 ms
Jun 20, 2026105 ms
Jun 27, 2026107 ms
Jul 4, 2026108 ms
Jul 11, 2026103 ms
Jul 18, 2026100 ms
Jul 25, 202693 ms
Aug 1, 202692 ms
Aug 8, 202690 ms
Aug 15, 202684 ms
Aug 22, 202687 ms
Aug 29, 202679 ms
Sep 5, 202678 ms
Sep 12, 202678 ms
Sep 19, 202676 ms
Sep 26, 202679 ms
Oct 3, 202679 ms
Oct 10, 202684 ms
Oct 17, 202684 ms
Oct 24, 202679 ms
Oct 31, 202679 ms
Nov 7, 202675 ms
Nov 14, 202673 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 allenandgledhill.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. allenandgledhill.com at 0.8 s0.8 s
  2. allenandgledhill.com at 1.6 s1.6 s
  3. allenandgledhill.com at 2.5 s2.5 s
  4. allenandgledhill.com at 3.3 s3.3 s
  5. allenandgledhill.com at 4.1 s4.1 s
  6. allenandgledhill.com at 4.9 s4.9 s
  7. allenandgledhill.com at 5.8 s5.8 s
  8. allenandgledhill.com at 6.6 s6.6 s

Speed

6 to fix39
  • Reduce unused JavaScript

    1.4 s · 1.2 MB

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

  • Font display

    2.1 s

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

  • Mobile performance score: 39

    39/100

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

  • Improve image delivery

    600 ms · 1.2 MB

    8 images could be 1.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 600 ms faster on a phone.

  • Minify JavaScript

    591 KiB

    591 KiB could be saved by minifying JavaScript.

  • Google Tag Manager adds 370 ms

    370 ms

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

  • 3 third-party services on the page

    3 third-party services load with your homepage (Google Tag Manager, Google Analytics and Other Google APIs/SDKs), adding 470 KiB and 370 ms of main-thread time.

  • 4 long tasks on the main thread

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

  • Document request latency

    30 KiB

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

  • Reduce unused CSS

    13 KiB

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

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

  • Minify CSS

    5 KiB

    5 KiB could be saved by minifying CSS.

2 checks passed
  • Main-thread work: 0.9 s

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

  • Server response: 97 ms

    97 ms

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

Core Web Vitals

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

  • Real-user FCP: 3.3 s

    3.3 s

    Real visitors see the first content after 3.3 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 2.5 s

    2.5 s

    Real visitors wait 2.5 s for your server to start answering (75th percentile). Good is under 800 ms.

  • Largest Contentful Paint: 7.5 s

    7.5 s

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

  • Speed Index: 8.9 s

    8.9 s

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

  • Cumulative Layout Shift: 0.465

    0.465

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

  • First Contentful Paint: 3.2 s

    3.2 s

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

  • Time to Interactive: 7.6 s

    7.6 s

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

  • Real-user LCP: 3.6 s

    3.6 s

    Real visitors wait 3.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • 9 images without width and height

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

4 checks passed
  • Real-user CLS: 0.09

    0.09

    For real visitors the layout shifts by 0.09 (75th percentile). Good is under 0.1.

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

    -18%

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

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

    -15%

    Over the last 25 four-week periods to 2026-11-14, 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).

  • Total Blocking Time: 181 ms

    181 ms

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

Images and page weight

5 to fix43
  • 1 image over 500 KB

    ag-singapore-2.png weighs 567 KiB. On a phone connection a single image that size takes seconds.

  • Page weight: 3.9 MB in 45 requests

    3.9 MB

    Your homepage downloads 3.9 MB in 45 requests on a phone: images 1.9 MB (15), scripts 1.9 MB (18) and fonts 75 KiB (4). Under 2 MB keeps phones on slow connections fast.

  • 12 images in older formats

    12 images (1.9 MB) 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.

  • 4 images below the first screen load straight away

    4 images further down the page (652 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 6 images far larger than shown

    185 KiB

    6 images are downloaded at several times the size a phone draws them, for example singapore_kh_5.jpg at 1,200 px wide, shown at 360 px. Resized copies would save about 185 KiB.

  • About 1.1 g of CO₂ per visit

    1.12 g

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

Accessibility

6 to fixGoogle 7990
  • Certain ARIA roles must be contained by particular parents (6 elements)

    Certain ARIA roles must be contained by particular parents: 6 elements on the page fail this check, rated critical by axe-core.

  • 17 text elements with low contrast

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

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

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

  • 2 links without text

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

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

2 checks passed
  • Every image has alt text

    All 14 images in the HTML carry an alt attribute.

  • 36 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: 36 passed and 5 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

5 to fixGoogle 8582
  • Title is short (22 characters)

    Your title is only 22 characters: “Home: Allen & Gledhill”. 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.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 6 links with vague text

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

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • 80 internal links, 9 external

    The homepage links to 80 pages on allenandgledhill.com and 9 external pages.

5 checks passed
  • Meta description: 145 characters

    Your meta description is 145 characters: “Allen & Gledhill is one of the largest and leading law firms in Singapore, with a notable and increasing presence in th…”.

  • One H1 headline

    Your main headline reads: “Unlimited Frontiers”.

  • Canonical URL set

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

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

AI search readiness

1 to fix88
  • 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.

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.

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://www.allenandgledhill.com/llms.txt (21 KiB, 0 links, though it should open with a “# Title” line), a plain-text guide to the site for AI tools.

Other pages

3 to fix88
  • 4 pages share a meta description

    https://www.allenandgledhill.com/sg, https://www.allenandgledhill.com/vn, https://www.allenandgledhill.com/cn and https://www.allenandgledhill.com/about-us 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://www.allenandgledhill.com/practices/china-practice-%E4%B8%AD%E5%9B%BD%E4%B8%9A%E5%8A%A1, whose canonical is https://www.allenandgledhill.com/practices/china-practice-%25E4%25B8%25AD%25E5%259B%25BD%25E4%25B8%259A%25E5%258A%25A1. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 1 page without an H1

    https://www.allenandgledhill.com/cn has no <h1> headline, so visitors and search engines get no clear main topic.

  • 3 pages slow to respond

    https://www.allenandgledhill.com/about-us, https://www.allenandgledhill.com/practices and https://www.allenandgledhill.com/perspectives took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 65 found) and read each the way a search engine does.

5 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • 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 15 pages that loaded have a <title>.

Best practices

3 to fixGoogle 9671
  • 1 broken image

    1 image failed to load on a phone, for example https://www.allenandgledhill.com/media/15860/alb-asia-top-50-2026_737-x-553.jpg?anchor=center&mode=crop&width=1200&height=900&rnd=134395757640000000.

  • 14 small tap targets

    14 of 27 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'call')”.

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix56
  • 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 calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • Thin social proof

    Social proof on the homepage: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

  • Only about 233 words

    The homepage has only about 233 words of visible text; thin pages give Google and first-time buyers little to go on.

  • No opening hours

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

  • 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 risk reducer

    No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

3 checks passed
  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

  • Phone number on the homepage

    Your phone number is on the homepage.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads Google Ads, 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.

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

  • 5 other companies contacted

    Loading the homepage contacts 5 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 allenandgledhill.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
jQuery
Analytics
Google Analytics | Google Tag Manager
Hosting
Imperva

Hiring

Hiring
1 open role
Job board
careers page

Company

Founded
1902
Headquarters
Singapore

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 45 issues on allenandgledhill.com, including 16 speed issues, 5 SEO issues and 5 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