Website review, no card needed

alaminuk.com logo

alaminuk.com website review

Visit site (opens in a new tab)Reviewed 19 October 202634 issues · 66 checks

This review found 34 issues worth fixing on alaminuk.com, 16 of them high impact, across 66 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

Full-page screenshot of alaminuk.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. alaminuk.com at 0.7 s0.7 s
  2. alaminuk.com at 1.4 s1.4 s
  3. alaminuk.com at 2.0 s2.0 s
  4. alaminuk.com at 2.7 s2.7 s
  5. alaminuk.com at 3.4 s3.4 s
  6. alaminuk.com at 4.1 s4.1 s
  7. alaminuk.com at 4.8 s4.8 s
  8. alaminuk.com at 5.4 s5.4 s

Speed

10 to fix19
  • Reduce unused JavaScript

    12.0 s · 2.3 MB

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

  • Improve image delivery

    1.1 s · 441 KiB

    13 images could be 441 KiB 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.

  • Use efficient cache lifetimes

    1.1 s · 257 KiB

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

  • Mobile performance score: 19

    19/100

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

  • Main-thread work: 6.4 s

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

  • 7 third-party services on the page

    7 third-party services load with your homepage (Google CDN, Other Google APIs/SDKs and cdn-apple.com and others), adding 3.9 MB and 120 ms of main-thread time.

  • 18 long tasks on the main thread

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

  • touch2success.com adds 1 ms

    1 ms

    touch2success.com costs a phone 1 ms of main-thread work and 2.8 MB 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.

  • Other Google APIs/SDKs adds 41 ms

    41 ms

    Other Google APIs/SDKs costs a phone 41 ms of main-thread work and 600 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.

  • foodhub.com adds 0 ms

    0 ms

    foodhub.com costs a phone 0 ms of main-thread work and 427 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.

  • Minify JavaScript

    130 ms · 2 KiB

    2 KiB could be saved by minifying JavaScript.

  • Reduce unused CSS

    10 KiB

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

1 checks passed
  • Server response: 3 ms

    3 ms

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

Core Web Vitals

6 to fix17
  • Largest Contentful Paint: 45.2 s

    45.2 s

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

  • Speed Index: 23.7 s

    23.7 s

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

  • Time to Interactive: 47.7 s

    47.7 s

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

  • Cumulative Layout Shift: 1.07

    1.07

    The layout shifts by 1.07 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.

  • Total Blocking Time: 618 ms

    618 ms

    Scripts block taps and scrolling for 618 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.

Images and page weight

1 to fix33
  • Page weight: 9.2 MB in 154 requests

    9.2 MB

    Your homepage downloads 9.2 MB in 154 requests on a phone: scripts 5.3 MB (79), images 3.2 MB (23) and other files 610 KiB (46). Under 2 MB keeps phones on slow connections fast.

  • About 2.6 g of CO₂ per visit

    2.61 g

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

Accessibility

4 to fixGoogle 9092
  • Documents must have <title> element to aid in navigation (1 element)

    Documents must have <title> element to aid in navigation: 1 element on the page fails this check, rated serious by axe-core.

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

  • All page content should be contained by landmarks (2 elements)

    All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.

  • Headings should not be empty (1 element)

    Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

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

    Elements with visible text labels do not have matching accessible names. (1 element).

2 checks passed
  • Every image has alt text

    All 1 image in the HTML carry an alt attribute.

  • 31 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: 31 passed and 4 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 9294
  • Structured data has 1 problem

    Structured data found (ImageObject, Restaurant, WebPage and WebSite) but with 1 problem, for example “WebPage: url is not an absolute URL ("alaminuk.com/")”.

  • Only 0 internal links

    The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.

  • Open Graph partly set

    Open Graph is missing og:title and og:description, so shared links fall back to guesses.

  • No X (Twitter) card tag

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

6 checks passed
  • Meta description: 142 characters

    Your meta description is 142 characters: “Alamin Tandoori is your go-to for authentic Indian takeaway in Reading. Order online and enjoy delicious food delivered…”.

  • One H1 headline

    Your main headline reads: “Alamin Tandoori | Indian Takeaway in Reading | Order Food Online”.

  • Title: 64 characters

    Your title is a healthy 64 characters: “Alamin Tandoori | Indian Takeaway in Reading | Order Food Online”.

  • Canonical URL set

    The canonical URL is https://alaminuk.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://alaminuk.com/sitemap.xml.

AI search readiness

100
  • No llms.txt

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

2 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 contact details; sameAs (social profiles) and description would complete it.

Best practices

4 to fixGoogle 4685
  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Authorization will not be covered by the wildcard symbol (*) in CORS `Access-Control-Allow-Headers`…”).

  • 1 third-party cookie

    1 third-party cookie is 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 “BackHandler is not supported on web and should not be used.”.

  • 15 distorted images

    15 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

  • Missing source maps

    Large scripts ship without source maps.

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

  • 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

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

  • No phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • Thin social proof

    Social proof on the homepage: a star rating. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No analytics detected

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

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

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

2 checks passed
  • Opening hours shown

    Your opening hours are on the homepage.

  • 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

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

  • 9 other companies contacted

    Loading the homepage contacts 9 hosts 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 alaminuk.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Go beyond the website

What your $25 Growth Playbook adds

This review found 34 issues on alaminuk.com, including 16 speed issues, 2 SEO issues and 7 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