nida.es website review

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

8 third-party services load with your homepage (channel.io, Facebook and Google Tag Manager and others), adding 1.5 MB and 1.7 s of main-thread time.

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

3 files block the first paint until they finish downloading. Deferring or inlining them could save about 950 ms.

channel.io costs a phone 852 ms of main-thread work and 379 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.

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

Facebook costs a phone 389 ms of main-thread work and 282 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.

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

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

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

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

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

Shopify costs a phone 85 ms of main-thread work and 479 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.

12 images could be 233 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.

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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

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

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

Scripts block taps and scrolling for 884 ms in total while the page loads. Good is under 200 ms.

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

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

Your homepage downloads 4.5 MB in 261 requests on a phone: images 2.1 MB (103), scripts 1.3 MB (58) and other files 863 KiB (89). Under 2 MB keeps phones on slow connections fast.

20260_Hero_Banner_MO_3.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

1 image further down the page (28 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

Scrollable region must have keyboard access: 12 elements on the page fail this check, rated serious by axe-core.

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

4 tap targets are too small or too close together to hit reliably with a finger.

1 link inside paragraphs relies on colour alone to stand out.

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

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

Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.

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.

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

Elements with role="dialog" or role="alertdialog" do not have accessible names. (1 element).

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

There are 2 <h1> headlines (“Experience Next Level of Hydration” and “Four Vitamins. Glowing Skin.”). One clear main headline is easier for people and search engines.

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

The homepage links to 69 pages on nida.es and 5 external pages.

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

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

15 of 51 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

2 errors were logged to the browser console while the page loaded, for example “Cannot set properties of null (setting 'textContent')”.

HSTS is set, but max-age is 91 days; one year is the recommended minimum.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

nida.co has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

The homepage carries about 625 words of visible text.

nida.es has no DMARC record, so nothing tells receivers what to do with mail that fails SPF or DKIM. Gmail and Yahoo require DMARC from bulk senders.

nida.es has no SPF record, so mail servers can't tell which servers may send email as you. Your mail lands in spam more often, and anyone can send mail pretending to be you.

We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

nida.es has no MX record, so it receives no email. SPF -all and DMARC reject still matter: they stop others sending mail as you.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, Meta Pixel, Pinterest Tag and TikTok Pixel (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.

Opening the homepage sets 19 cookies (measured from a US location before any click).

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.

Loading the homepage contacts 26 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.