Website review, no card needed

admireworks.com logo

admireworks.com website review

Visit site (opens in a new tab)Reviewed 17 November 202622 issues · 68 checks

This review found 22 issues worth fixing on admireworks.com, 5 of them high impact, across 68 checks. The most urgent: page weight: 33.7 MB in 34 requests. 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 admireworks.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. admireworks.com at 0.4 s0.4 s
  2. admireworks.com at 0.8 s0.8 s
  3. admireworks.com at 1.1 s1.1 s
  4. admireworks.com at 1.5 s1.5 s
  5. admireworks.com at 1.9 s1.9 s
  6. admireworks.com at 2.3 s2.3 s
  7. admireworks.com at 2.6 s2.6 s
  8. admireworks.com at 3.0 s3.0 s

Speed

6 to fix94
  • Improve image delivery

    10.6 MB

    10 images could be 10.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 6 third-party services on the page

    6 third-party services load with your homepage (Google Tag Manager, Clarity and apollo.io and others), adding 25.2 MB and 373 ms of main-thread time.

  • Other Google APIs/SDKs adds 0 ms

    0 ms

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

  • Use efficient cache lifetimes

    2.0 MB

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

  • Font display

    500 ms

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

  • Google Tag Manager adds 267 ms

    267 ms

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

  • 4 long tasks on the main thread

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

  • Reduce unused JavaScript

    110 KiB

    About 110 KiB of JavaScript is downloaded but never used on this page.

  • Render-blocking requests

    100 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 100 ms.

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

3 checks passed
  • Mobile performance score: 94

    94/100

    Your mobile performance score is 94. That is in Google's “good” band (90 and up).

  • Main-thread work: 1.0 s

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

  • Server response: 3 ms

    3 ms

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

Core Web Vitals

2 to fix97
  • Time to Interactive: 6.5 s

    6.5 s

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

  • Speed Index: 4.7 s

    4.7 s

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

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

4 checks passed
  • Total Blocking Time: 184 ms

    184 ms

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

  • Cumulative Layout Shift: 0

    0

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

  • First Contentful Paint: 0.9 s

    0.9 s

    The first text or image appears after 0.9 s, inside the 1.8 s “good” threshold.

  • Largest Contentful Paint: 0.9 s

    0.9 s

    Your largest element renders in 0.9 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Admireworks is a venture services agency headquartered in D…”.

Images and page weight

5 to fix18
  • Page weight: 33.7 MB in 34 requests

    33.7 MB

    Your homepage downloads 33.7 MB in 34 requests on a phone: media 22.5 MB (2), images 10.7 MB (11) and scripts 300 KiB (5). Under 2 MB keeps phones on slow connections fast.

  • 8 images far larger than shown

    10.2 MB

    8 images are downloaded at several times the size a phone draws them, for example fouad.jpg at 4,480 px wide, shown at 171 px. Resized copies would save about 10.2 MB.

  • 2 images over 500 KB

    2 images weigh 9.5 MB together. On a phone connection a single image that size takes seconds.

  • 10 images in older formats

    10 images (10.7 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.

  • 10 images below the first screen load straight away

    10 images further down the page (10.7 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 9.5 g of CO₂ per visit

    9.55 g

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

Accessibility

3 to fixGoogle 8494
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

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

  • 6 links without text

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 70 images in the HTML carry an alt attribute.

  • 38 automated accessibility rules passed

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

SEO

3 to fixGoogle 10090
  • Meta description is long (193 characters)

    Your meta description is 193 characters; Google truncates after about 160, so the end of your pitch is cut.

  • Structured data has 5 problems

    Structured data found ((untyped), Organization and WebSite) but with 5 problems, for example “Organization: url points at a different host (https://admire8.com)”.

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • 11 internal links, 10 external

    The homepage links to 11 pages on admireworks.com and 10 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “Admirable Venture Services”.

  • Title: 60 characters

    Your title is a healthy 60 characters: “Admireworks | Venture services agency headquartered in Dubai”.

  • Canonical URL set

    The canonical URL is https://admireworks.com/.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

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

AI search readiness

100
4 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: 5 of 6 facts

    Your Organization JSON-LD gives name, url, sameAs (social profiles), description and contact details; logo would complete it.

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://admireworks.com/llms.txt (1 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

100
  • 4 internal pages checked

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

7 checks passed
  • Linked pages load

    All 4 pages we checked loaded without an error.

  • Canonical URLs point to themselves

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

  • Every page has a meta description

    All 4 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 4 pages that loaded have a <title>.

Best practices

1 to fixGoogle 10092
  • 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”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix90
  • No analytics detected

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

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

    The homepage carries about 422 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Book a clarity call”.

  • 4 calls to action

    The homepage has 4 calls to action, for example “Contact”, “Book a clarity call” and “Start the conversation”.

  • Social proof on the page

    Social proof on the homepage: 1 testimonial or review block, 60 customer or partner logos, 2 trust badges and “More than 300 brands”.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 1 email link.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

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

  • 5 cookies set on arrival

    5

    Opening the homepage sets 5 cookies, 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.

  • 11 other companies contacted

    Loading the homepage contacts 11 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 admireworks.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
Tailwind CSS
Hosting
Google

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 22 issues on admireworks.com, including 8 speed issues, 3 SEO issues and 1 conversion gap. 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