Website review, no card needed

reigjofre.com logo

reigjofre.com website review

Visit site (opens in a new tab)Reviewed 19 November 202632 issues · 79 checks

This review found 32 issues worth fixing on reigjofre.com, 11 of them high impact, across 79 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
2.4 s2.0 sMay 30Nov 142.3 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20262.1 s
Jun 6, 20262.1 s
Jun 13, 20262.1 s
Jun 20, 20262.2 s
Jun 27, 20262.2 s
Jul 4, 20262.2 s
Jul 11, 20262.1 s
Jul 18, 20262.2 s
Jul 25, 20262.2 s
Aug 1, 20262.3 s
Aug 8, 20262.4 s
Aug 15, 20262.4 s
Aug 22, 20262.3 s
Aug 29, 20262.1 s
Sep 5, 20262.1 s
Sep 12, 20262.1 s
Sep 19, 20262.2 s
Sep 26, 20262.2 s
Oct 3, 20262.2 s
Oct 10, 20262.2 s
Oct 17, 20262.2 s
Oct 24, 20262.3 s
Oct 31, 20262.3 s
Nov 7, 20262.3 s
Nov 14, 20262.3 s
Real-visitor tap response (INP)75th percentile, phones
128 ms110 msMay 30Nov 14114 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026126 ms
Jun 6, 2026122 ms
Jun 13, 2026123 ms
Jun 20, 2026124 ms
Jun 27, 2026120 ms
Jul 4, 2026120 ms
Jul 11, 2026118 ms
Jul 18, 2026120 ms
Jul 25, 2026120 ms
Aug 1, 2026121 ms
Aug 8, 2026122 ms
Aug 15, 2026120 ms
Aug 22, 2026121 ms
Aug 29, 2026115 ms
Sep 5, 2026113 ms
Sep 12, 2026121 ms
Sep 19, 2026115 ms
Sep 26, 2026118 ms
Oct 3, 2026121 ms
Oct 10, 2026115 ms
Oct 17, 2026117 ms
Oct 24, 2026117 ms
Oct 31, 2026117 ms
Nov 7, 2026112 ms
Nov 14, 2026114 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 reigjofre.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. reigjofre.com at 1.3 s1.3 s
  2. reigjofre.com at 2.5 s2.5 s
  3. reigjofre.com at 3.8 s3.8 s
  4. reigjofre.com at 5.1 s5.1 s
  5. reigjofre.com at 6.3 s6.3 s
  6. reigjofre.com at 7.6 s7.6 s
  7. reigjofre.com at 8.9 s8.9 s
  8. reigjofre.com at 10.2 s10.2 s

Speed

9 to fix62
  • Reduce unused JavaScript

    5.4 s · 700 KiB

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

  • Use efficient cache lifetimes

    3.1 s · 1.2 MB

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

  • Render-blocking requests

    2.3 s

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

  • Reduce unused CSS

    1.4 s · 194 KiB

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

  • Mobile performance score: 62

    62/100

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

  • 5 third-party services on the page

    5 third-party services load with your homepage (Google CDN, Google Tag Manager and Other Google APIs/SDKs and others), adding 1.2 MB and 381 ms of main-thread time.

  • Improve image delivery

    150 ms · 347 KiB

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

  • Google CDN adds 264 ms

    264 ms

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

  • Legacy JavaScript

    100 ms · 38 KiB

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

  • 5 long tasks on the main thread

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

  • 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: 2 ms

    2 ms

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

Core Web Vitals

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

  • Largest Contentful Paint: 14.9 s

    14.9 s

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

  • Time to Interactive: 15.7 s

    15.7 s

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

  • Speed Index: 9.8 s

    9.8 s

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

  • Real-user TTFB: 1.1 s

    1.1 s

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

  • First Contentful Paint: 2.1 s

    2.1 s

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

  • 4 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -9%

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

  • Largest content (LCP) got 10% slower for real visitors

    +10%

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

6 checks passed
  • Real-user LCP: 2.4 s

    2.4 s

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

  • Real-user INP: 113 ms

    113 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 1.5 s

    1.5 s

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

  • Cumulative Layout Shift: 0.1

    0.1

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

  • Total Blocking Time: 39 ms

    39 ms

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

Images and page weight

3 to fix68
  • Page weight: 3.0 MB in 67 requests

    3.0 MB

    Your homepage downloads 3.0 MB in 67 requests on a phone: scripts 1.3 MB (23), images 675 KiB (23) and fonts 430 KiB (8). Under 2 MB keeps phones on slow connections fast.

  • 4 images below the first screen load straight away

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

  • 1 image far larger than shown

    2 KiB

    1 image is downloaded at several times the size a phone draws it, for example home-asset-01.jpg at 960 px wide, shown at 318 px. Resized copies would save about 2 KiB.

  • 4 images in older formats

    4 images (487 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 0.9 g of CO₂ per visit

    0.86 g

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

Accessibility

4 to fixGoogle 9195
  • 5 text elements with low contrast

    5 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 (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • 9 links without text

    9 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 (h3 → h5, h3 → h5 and h3 → h5), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 19 images in the HTML carry an alt attribute.

  • 46 automated accessibility rules passed

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

SEO

2 to fixGoogle 8588
  • No meta description

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

  • 5 links with vague text

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

  • Open Graph partly set

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

  • 58 internal links, 25 external

    The homepage links to 58 pages on reigjofre.com and 25 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “We develop, produce, market, and distribute essential healthcare solutions—ranging from critical, specialized treatment…”.

  • Title: 33 characters

    Your title is a healthy 33 characters: “Homepage | Laboratorio Reig Jofre”.

  • Canonical URL set

    The canonical URL is https://reigjofre.com/en/.

  • Structured data in place

    Structured data found: BreadcrumbList, Organization, 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://reigjofre.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: 4 of 6 facts

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

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

3 to fix83
  • 2 pages share a title

    https://reigjofre.com/en/investors/the-share and https://reigjofre.com/en/investors/the-share/stock-watch all use the title “Stock Watch | Laboratorio Reig Jofre”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 13 pages without a meta description

    https://reigjofre.com/en/who-we-are, https://reigjofre.com/en/innovation, https://reigjofre.com/en/innovation/international-projects, https://reigjofre.com/en/innovation/national-projects, https://reigjofre.com/en/products/healthcare-professionals-consumers and https://reigjofre.com/en/products/healthcare-professionals-consumers/markets-uk and 7 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://reigjofre.com/en/investors/the-share, whose canonical is https://reigjofre.com/en/investors/the-share/stock-watch. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 11 pages slow to respond

    https://reigjofre.com/en/innovation, https://reigjofre.com/en/innovation/international-projects, https://reigjofre.com/en/products/healthcare-professionals-consumers, https://reigjofre.com/en/products/healthcare-professionals-consumers/markets-uk, https://reigjofre.com/en/investors and https://reigjofre.com/en/investors/the-share 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 43 found) and read each the way a search engine does.

4 checks passed
  • Linked pages load

    14 pages of 15 loaded without an error (the rest turned automated requests away).

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

Best practices

2 to fixGoogle 9687
  • 16 small tap targets

    16 of 29 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: net::ERR_TUNNEL_CONNECTION_FAILED”.

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix83
  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

    The homepage carries about 337 words of visible text.

5 checks passed
  • Clear next step on the first screen

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

  • 7 calls to action

    The homepage has 7 calls to action, for example “Contact”, “Contact form” and “Join our team”.

  • 1 short form

    A short form (0 fields at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

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

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

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

  • 2 cookies set on arrival

    2

    Opening the homepage sets 2 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 reigjofre.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

  • The footer still says © 2025.

Stack

CMS
WordPress
Framework
jQuery
Analytics
Google Analytics
Hosting
DinaHosting S.L.

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 32 issues on reigjofre.com, including 16 speed issues, 2 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