Website review, no card needed

royal-lab.net logo

royal-lab.net website review

Visit site (opens in a new tab)Reviewed 19 November 202643 issues · 93 checks

This review found 43 issues worth fixing on royal-lab.net, 15 of them high impact, across 93 checks. The most urgent: improve image delivery. 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
3.1 s2.8 sMay 30Nov 143.0 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20263.0 s
Jun 6, 20263.0 s
Jun 13, 20263.0 s
Jun 20, 20263.0 s
Jun 27, 20263.0 s
Jul 4, 20263.0 s
Jul 11, 20263.0 s
Jul 18, 20263.0 s
Jul 25, 20263.0 s
Aug 1, 20263.0 s
Aug 8, 20263.0 s
Aug 15, 20262.9 s
Aug 22, 20262.9 s
Aug 29, 20262.9 s
Sep 5, 20262.8 s
Sep 12, 20262.9 s
Sep 19, 20262.9 s
Sep 26, 20262.9 s
Oct 3, 20262.9 s
Oct 10, 20262.9 s
Oct 17, 20262.8 s
Oct 24, 20262.8 s
Oct 31, 20262.9 s
Nov 7, 20262.9 s
Nov 14, 20263.0 s
Real-visitor tap response (INP)75th percentile, phones
215 ms134 msMay 30Nov 14147 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026205 ms
Jun 6, 2026206 ms
Jun 13, 2026203 ms
Jun 20, 2026203 ms
Jun 27, 2026204 ms
Jul 4, 2026201 ms
Jul 11, 2026202 ms
Jul 18, 2026196 ms
Jul 25, 2026198 ms
Aug 1, 2026200 ms
Aug 8, 2026197 ms
Aug 15, 2026190 ms
Aug 22, 2026176 ms
Aug 29, 2026167 ms
Sep 5, 2026157 ms
Sep 12, 2026150 ms
Sep 19, 2026149 ms
Sep 26, 2026145 ms
Oct 3, 2026147 ms
Oct 10, 2026147 ms
Oct 17, 2026144 ms
Oct 24, 2026143 ms
Oct 31, 2026143 ms
Nov 7, 2026143 ms
Nov 14, 2026147 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 royal-lab.net (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. royal-lab.net at 2.4 s2.4 s
  2. royal-lab.net at 4.9 s4.9 s
  3. royal-lab.net at 7.3 s7.3 s
  4. royal-lab.net at 9.8 s9.8 s
  5. royal-lab.net at 12.2 s12.2 s
  6. royal-lab.net at 14.6 s14.6 s
  7. royal-lab.net at 17.1 s17.1 s
  8. royal-lab.net at 19.5 s19.5 s

Speed

10 to fix57
  • Improve image delivery

    2.1 s · 697 KiB

    15 images could be 697 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.1 s faster on a phone.

  • Render-blocking requests

    2.8 s

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

  • Reduce unused JavaScript

    2.3 s · 413 KiB

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

  • Main-thread work: 5.5 s

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

  • 4,827 HTML elements

    The page has 4,827 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Use efficient cache lifetimes

    800 ms · 371 KiB

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

  • Mobile performance score: 57

    57/100

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

  • Reduce unused CSS

    600 ms · 128 KiB

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

  • Minify JavaScript

    300 ms · 49 KiB

    49 KiB could be saved by minifying JavaScript.

  • Google Maps adds 112 ms

    112 ms

    Google Maps costs a phone 112 ms of main-thread work and 457 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.

  • 7 third-party services on the page

    7 third-party services load with your homepage (Google Maps, GoDaddy and trustedsite.com and others), adding 522 KiB and 160 ms of main-thread time.

  • 3 long tasks on the main thread

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

  • Font display

    50 ms

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

  • Legacy JavaScript

    16 KiB

    Polyfills for old browsers add 16 KiB JavaScript that modern phones do not need.

  • Minify CSS

    9 KiB

    9 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: 17 ms

    17 ms

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

Core Web Vitals

10 to fix33
  • 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 CLS: 0.28

    0.28

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

  • Largest Contentful Paint: 19.5 s

    19.5 s

    Your largest element takes 19.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Royal Lab Dependable Results Led by Enthusiastic Profession…”.

  • Speed Index: 16.4 s

    16.4 s

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

  • Time to Interactive: 19.7 s

    19.7 s

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

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

  • Real-user LCP: 4.0 s

    4.0 s

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

  • Real-user FCP: 2.7 s

    2.7 s

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

  • Real-user TTFB: 1.3 s

    1.3 s

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

  • 27 images without width and height

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

  • Largest content (LCP) held steady for real visitors

    -2%

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

4 checks passed
  • Real-user INP: 171 ms

    171 ms

    Real visitors wait 171 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

    -29%

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

  • Total Blocking Time: 164 ms

    164 ms

    Scripts block the page for only 164 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

2 to fix78
  • Page weight: 3.6 MB in 157 requests

    3.6 MB

    Your homepage downloads 3.6 MB in 157 requests on a phone: images 1.9 MB (26), scripts 1.0 MB (63) and fonts 340 KiB (6). Under 2 MB keeps phones on slow connections fast.

  • 10 images below the first screen load straight away

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

  • 6 images in older formats

    6 images (456 KiB) 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.

  • About 1.0 g of CO₂ per visit

    1.02 g

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

1 checks passed
  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

6 to fixGoogle 8592
  • 1 button without a name

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

  • 2 text elements with low contrast

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

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

    All page content should be contained by landmarks: 166 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.

  • 3 links without text

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 23 images in the HTML carry an alt attribute.

  • 45 automated accessibility rules passed

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

SEO

5 to fixGoogle 7775
  • No meta description

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

  • Title is short (16 characters)

    Your title is only 16 characters: “Home - Royal Lab”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 6 H1 headlines

    There are 6 <h1> headlines (“Royal Lab Dependable Results”, “Discover our 24/7 Accessible Laboratory” and “Boundless Services at Royal Lab”). One clear main headline is easier for people and search engines.

  • 5 links crawlers can't follow

    5 links have no real href, so search engines can't follow them.

  • 2 links with vague text

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

  • 55 internal links, 14 external

    The homepage links to 55 pages on royal-lab.net and 14 external pages.

5 checks passed
  • Canonical URL set

    The canonical URL is https://royal-lab.net/.

  • Structured data in place

    Structured data found: BreadcrumbList, ImageObject, Organization, WebPage and WebSite.

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

  • XML sitemap found

    Your XML sitemap is reachable at https://royal-lab.net/sitemap.xml.

AI search readiness

1 to fix75
  • Most text only appears after JavaScript runs

    15%

    A phone browser shows 3,329 words, but the HTML your server sends has only 507. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

  • No llms.txt

    There is no https://royal-lab.net/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 sameAs (social profiles); description and contact details would complete it.

Other pages

3 to fix85
  • 15 pages without a meta description

    https://royal-lab.net/about-us, https://royal-lab.net/appointment, https://royal-lab.net/lab-test-packages, https://royal-lab.net/tests-precautions-1, https://royal-lab.net/branches and https://royal-lab.net/contact-us and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://royal-lab.net/ar/%d8%a7%d9%84%d8%b1%d8%a6%d9%8a%d8%b3%d9%8a%d8%a9, whose canonical is https://royal-lab.net/ar/%D8%A7%D9%84%D8%B1%D8%A6%D9%8A%D8%B3%D9%8A%D8%A9. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 14 pages without an H1

    https://royal-lab.net/about-us, https://royal-lab.net/appointment, https://royal-lab.net/lab-test-packages, https://royal-lab.net/tests-precautions-1, https://royal-lab.net/branches and https://royal-lab.net/contact-us and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 12 pages with very little text

    https://royal-lab.net/appointment, https://royal-lab.net/branches, https://royal-lab.net/contact-us, https://royal-lab.net/ar/%d8%a7%d9%84%d8%b1%d8%a6%d9%8a%d8%b3%d9%8a%d8%a9, https://royal-lab.net/online-approvals and https://royal-lab.net/lab-test-packages/bronze-package and 6 others have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 1 page slow to respond

    https://royal-lab.net/tests-precautions-1 took over 3 s to send its HTML from our server.

  • 15 internal pages checked

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

4 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • 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 9285
  • 12 small tap targets

    12 of 26 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 “Failed to load resource: the server responded with a status of 403 ()”.

  • 3 distorted images

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

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix83
  • Local business without LocalBusiness data

    Your homepage shows a map 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: 1 trust badge. 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 opening hours

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

  • About 3,329 words of copy

    The homepage carries about 3,329 words of visible text.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “LEARN MORE LEARN MORE” and “CONTACT US CONTACT US”.

  • 10 calls to action

    The homepage has 10 calls to action, for example “Contact Us”, “Book Home Visit Book Home Visit” and “Learn More Learn More”.

  • 1 short form

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

  • Direct contact links

    Visitors can reach you directly: 2 phone links and 2 email links.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

  • 6 cookies set on arrival

    6

    Opening the homepage sets 6 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.

  • 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 royal-lab.net, 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 43 issues on royal-lab.net, including 20 speed issues, 5 SEO issues and 3 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