Website review, no card needed

cytomed.ae logo

cytomed.ae website review

Visit site (opens in a new tab)Reviewed 3 November 202653 issues · 91 checks

This review found 53 issues worth fixing on cytomed.ae, 23 of them high impact, across 91 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

Real-visitor load time (LCP)75th percentile, phones
5.4 s3.9 sAug 29Sep 264.1 s
Show as table
DateReal-visitor load time (LCP)
Aug 29, 20265.3 s
Sep 5, 20265.2 s
Sep 12, 20265.2 s
Sep 19, 20265.2 s
Sep 26, 20264.1 s

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 cytomed.ae (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. cytomed.ae at 1.0 s1.0 s
  2. cytomed.ae at 2.1 s2.1 s
  3. cytomed.ae at 3.1 s3.1 s
  4. cytomed.ae at 4.2 s4.2 s
  5. cytomed.ae at 5.2 s5.2 s
  6. cytomed.ae at 6.3 s6.3 s
  7. cytomed.ae at 7.3 s7.3 s
  8. cytomed.ae at 8.4 s8.4 s

Speed

13 to fix55
  • Use efficient cache lifetimes

    4.8 s · 10.6 MB

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

  • Render-blocking requests

    5.4 s

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

  • Reduce unused JavaScript

    4.1 s · 482 KiB

    About 482 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.1 s faster on a phone.

  • Reduce unused CSS

    1.5 s · 250 KiB

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

  • Font display

    1.5 s

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

  • Improve image delivery

    400 ms · 955 KiB

    27 images could be 955 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 400 ms faster on a phone.

  • Mobile performance score: 55

    55/100

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

  • Document request latency

    650 ms · 85 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google CDN, Cloudflare CDN and jQuery CDN and others), adding 982 KiB and 584 ms of main-thread time.

  • Reduce initial server response time

    626 ms

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

  • Google CDN adds 369 ms

    369 ms

    Google CDN costs a phone 369 ms of main-thread work and 736 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.

  • Main-thread work: 2.1 s

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

  • Server response: 726 ms

    726 ms

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

  • Minify JavaScript

    290 ms · 33 KiB

    33 KiB could be saved by minifying JavaScript.

  • Minify CSS

    150 ms · 39 KiB

    39 KiB could be saved by minifying CSS.

  • Legacy JavaScript

    100 ms · 26 KiB

    Polyfills for old browsers add 26 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 100 ms faster on a phone.

  • 7 long tasks on the main thread

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

  • Duplicated JavaScript

    100 ms · 12 KiB

    12 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 100 ms faster on a phone.

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

Core Web Vitals

5 to fix66
  • Largest Contentful Paint: 20.1 s

    20.1 s

    Your largest element takes 20.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “INNOVATIVE LABORATORY SOLUTIONS”.

  • Time to Interactive: 26.4 s

    26.4 s

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

  • Speed Index: 14.0 s

    14.0 s

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

  • First Contentful Paint: 6.0 s

    6.0 s

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

  • 48 images without width and height

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

3 checks passed
  • Largest content (LCP) got 12% faster for real visitors

    -12%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 5.3 s to 4.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Total Blocking Time: 97 ms

    97 ms

    Scripts block the page for only 97 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).

Images and page weight

5 to fix18
  • Page weight: 12.0 MB in 159 requests

    12.0 MB

    Your homepage downloads 12.0 MB in 159 requests on a phone: images 9.8 MB (99), scripts 1.2 MB (23) and stylesheets 359 KiB (25). Under 2 MB keeps phones on slow connections fast.

  • 4 images over 500 KB

    4 images weigh 7.6 MB together. On a phone connection a single image that size takes seconds.

  • 6 images far larger than shown

    7.0 MB

    6 images are downloaded at several times the size a phone draws them, for example 004.jpg at 2,407 px wide, shown at 250 px. Resized copies would save about 7.0 MB.

  • 20 images in older formats

    20 images (8.6 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.

  • 22 images below the first screen load straight away

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

  • About 3.4 g of CO₂ per visit

    3.41 g

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

Accessibility

17 to fixGoogle 5979
  • 2 buttons without a name

    2 buttons have no accessible name, so screen readers announce just “button”.

  • Invalid ARIA attributes

    1 element use ARIA attributes their role does not allow, which confuses screen readers.

  • Certain ARIA roles must contain particular children (1 element)

    Certain ARIA roles must contain particular children: 1 element on the page fails 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.

  • ARIA toggle fields must have an accessible name (7 elements)

    ARIA toggle fields must have an accessible name: 7 elements on the page fail this check, rated serious by axe-core.

  • ARIA input fields must have an accessible name (5 elements)

    ARIA input fields must have an accessible name: 5 elements on the page fail this check, rated serious by axe-core.

  • Interactive controls must not be nested (5 elements)

    Interactive controls must not be nested: 5 elements on the page fail this check, rated serious by axe-core.

  • Malformed lists

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

  • 27 images without alt text

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

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

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

  • 8 links without text

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

  • Hidden but focusable

    2 elements hidden from screen readers can still receive keyboard focus.

  • 2 form fields without a label

    2 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • 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 marked as presentational should be consistently ignored (1 element)

    Elements marked as presentational should be consistently ignored: 1 element on the page fails this check, rated minor by axe-core.

  • Headings skip levels

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

1 checks passed
  • 46 automated accessibility rules passed

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

SEO

3 to fixGoogle 8580
  • No meta description

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

  • Title is short (29 characters)

    Your title is only 29 characters: “Cytomed | Healthcare Solution”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No social preview image

    No Open Graph image (also missing: og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 44 internal links, 11 external

    The homepage links to 44 pages on cytomed.ae and 11 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “WE SUPPORT LABORATORIES TO ACHIEVE ACCURATE & EFFICIENT RESULTS”.

  • Canonical URL set

    The canonical URL is https://cytomed.ae/.

  • Structured data in place

    Structured data found: Article, Organization, Person, WebPage and WebSite.

  • 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://cytomed.ae/sitemap_index.xml.

AI search readiness

1 to fix88
  • Organization data is thin (1 of 6 facts)

    Your Organization JSON-LD is missing url, logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

  • No llms.txt

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

  • Text is in the HTML

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

Other pages

3 to fix83
  • 16 pages share a title

    /, https://cytomed.ae/about, https://cytomed.ae/brandss, https://cytomed.ae/products, https://cytomed.ae/medical-division and https://cytomed.ae/laboratory-division and 10 others all use the title “Cytomed | Healthcare Solution”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 15 pages without a meta description

    https://cytomed.ae/about, https://cytomed.ae/brandss, https://cytomed.ae/products, https://cytomed.ae/medical-division, https://cytomed.ae/laboratory-division and https://cytomed.ae/industry-business-unit and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 12 pages without an H1

    https://cytomed.ae/about, https://cytomed.ae/brandss, https://cytomed.ae/products, https://cytomed.ae/medical-division, https://cytomed.ae/laboratory-division and https://cytomed.ae/industry-business-unit and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 11 pages slow to respond

    https://cytomed.ae/medical-division, https://cytomed.ae/laboratory-division, https://cytomed.ae/industry-business-unit, https://cytomed.ae/services, https://cytomed.ae/projects and https://cytomed.ae/media-events and 5 others took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

4 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

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

  • 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

2 to fixGoogle 8891
  • 5 JavaScript errors while loading

    5 errors were logged to the browser console while the page loaded, for example “Uncaught TypeError: Cannot read properties of undefined (reading 'fn')”.

  • 10 distorted images

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

  • 1 low-resolution image

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

2 checks passed
  • Tap targets are thumb-sized

    16 of 16 tappable elements near the top are at least 24 px.

  • 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: “19+ Brands”. 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.

  • A 11-field form

    Your longest form asks for 11 fields (0 required). Every extra field lowers completion.

  • 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 1,020 words of copy

    The homepage carries about 1,020 words of visible text.

2 checks passed
  • 3 calls to action

    The homepage has 3 calls to action, for example “Start search”, “Contact” and “+Contact Us”.

  • Direct contact links

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

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.

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

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 cytomed.ae, 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

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 53 issues on cytomed.ae, including 18 speed issues, 3 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