rocnarf.com website review

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

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

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

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

About 33 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

1 long task block the main thread while loading, the longest for 80 ms. During a long task the page ignores taps.

4 third-party services load with your homepage (Cloudflare CDN, FontAwesome CDN and Google Fonts and others), adding 394 KiB and 16 ms of main-thread time.

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

About 34 KiB of CSS is downloaded but never applied on this page.

Polyfills for old browsers add 9 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.

4 KiB could be saved by minifying JavaScript.

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 visitors wait 4.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

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

Your largest element takes 8.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Comprometidos con el cuidado de la…”.

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

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

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

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

The layout shifts by 0.151 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 111 ms to 113 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 4.7 s to 5.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

3 images are downloaded at several times the size a phone draws them, for example Maganyl-nuevos-sabores-mv.jpg at 1,400 px wide, shown at 310 px. Resized copies would save about 132 KiB.

3 images (199 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.

1 image further down the page (127 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 0.46 g of CO₂e: 54.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

1 image has no alt text, which hurts accessibility and image search.

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

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is 191 characters, so Google will cut it off around 60: “Rocnarf - Calidad y bienestar en cada medicamento | Comprometidos con el bienestar de los…”.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

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

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 27 pages on rocnarf.com and 16 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

There is no https://www.rocnarf.com/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.

https://www.rocnarf.com/cosecha-de-talentos-programa-de-pasantias, https://www.rocnarf.com/sobre-nosotros, https://www.rocnarf.com/responsabilidad-social, https://www.rocnarf.com/lideres-en-informacion, https://www.rocnarf.com/gente-rocnarf and https://www.rocnarf.com/farmacovigilancia and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.rocnarf.com/vademecum, whose canonical is https://www.rocnarf.com/vademecum-nuevos-lanzamientos. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.rocnarf.com/cosecha-de-talentos-programa-de-pasantias, https://www.rocnarf.com/sobre-nosotros, https://www.rocnarf.com/responsabilidad-social, https://www.rocnarf.com/lideres-en-informacion, https://www.rocnarf.com/gente-rocnarf and https://www.rocnarf.com/farmacovigilancia and 4 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.rocnarf.com/gente-rocnarf and https://www.rocnarf.com/productos took over 3 s to send their HTML from our server.

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

1 image failed to load on a phone, for example https://www.rocnarf.com/wp-content/uploads/2021/08/home-gente-rocnarf-480x322.jpg.

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

5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 403 ()”.

Chrome logged issues while loading the page (“Mixed content”).

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

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

Social proof on the homepage: 3 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

There is no form on the homepage, so every lead has to click through to another page first.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 313 words of visible text.

Opening the homepage sets 8 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 4 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.