Website review, no card needed
randstad.com.ar website review
Visit site (opens in a new tab)Reviewed 18 November 202639 issues · 83 checks
This review found 39 issues worth fixing on randstad.com.ar, 7 of them high impact, across 83 checks. The most urgent: fails Core Web Vitals for real visitors. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
77CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 2.4 s |
| Jun 6, 2026 | 2.4 s |
| Jun 13, 2026 | 2.4 s |
| Jun 20, 2026 | 2.4 s |
| Jun 27, 2026 | 2.5 s |
| Jul 4, 2026 | 2.5 s |
| Jul 11, 2026 | 2.6 s |
| Jul 18, 2026 | 2.6 s |
| Jul 25, 2026 | 2.4 s |
| Aug 1, 2026 | 2.3 s |
| Aug 8, 2026 | 2.2 s |
| Aug 15, 2026 | 2.1 s |
| Aug 22, 2026 | 2.0 s |
| Aug 29, 2026 | 2.0 s |
| Sep 5, 2026 | 1.9 s |
| Sep 12, 2026 | 2.0 s |
| Sep 19, 2026 | 2.0 s |
| Sep 26, 2026 | 2.0 s |
| Oct 3, 2026 | 2.0 s |
| Oct 10, 2026 | 2.0 s |
| Oct 17, 2026 | 1.9 s |
| Oct 24, 2026 | 1.9 s |
| Oct 31, 2026 | 1.9 s |
| Nov 7, 2026 | 1.9 s |
| Nov 14, 2026 | 1.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 233 ms |
| Jun 6, 2026 | 235 ms |
| Jun 13, 2026 | 235 ms |
| Jun 20, 2026 | 237 ms |
| Jun 27, 2026 | 236 ms |
| Jul 4, 2026 | 235 ms |
| Jul 11, 2026 | 234 ms |
| Jul 18, 2026 | 232 ms |
| Jul 25, 2026 | 233 ms |
| Aug 1, 2026 | 236 ms |
| Aug 8, 2026 | 239 ms |
| Aug 15, 2026 | 242 ms |
| Aug 22, 2026 | 244 ms |
| Aug 29, 2026 | 245 ms |
| Sep 5, 2026 | 244 ms |
| Sep 12, 2026 | 243 ms |
| Sep 19, 2026 | 239 ms |
| Sep 26, 2026 | 241 ms |
| Oct 3, 2026 | 244 ms |
| Oct 10, 2026 | 248 ms |
| Oct 17, 2026 | 258 ms |
| Oct 24, 2026 | 261 ms |
| Oct 31, 2026 | 260 ms |
| Nov 7, 2026 | 260 ms |
| Nov 14, 2026 | 260 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
How it loaded on a phone
0.5 s
1.0 s
1.5 s
2.0 s
2.4 s
2.9 s
3.4 s
3.9 s
Speed
Use efficient cache lifetimes
750 ms · 428 KiB31 files are served with short cache lifetimes, so returning visitors download them again (428 KiB).
5 third-party services on the page
5 third-party services load with your homepage (Google Tag Manager, central.chat and Optanon and others), adding 1.6 MB and 994 ms of main-thread time.
Mobile performance score: 75
75/100Your mobile performance score is 75. Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
750 ms5 files block the first paint until they finish downloading. Deferring or inlining them could save about 750 ms.
Reduce unused JavaScript
660 KiBAbout 660 KiB of JavaScript is downloaded but never used on this page.
Google Tag Manager adds 450 ms
450 msGoogle Tag Manager costs a phone 450 ms of main-thread work and 366 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.
central.chat adds 364 ms
364 mscentral.chat costs a phone 364 ms of main-thread work and 971 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.
Improve image delivery
399 KiB6 images could be 399 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Main-thread work: 3.1 s
A phone's processor spends 3.1 s on main-thread work while loading, 1.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
1,834 HTML elements
The page has 1,834 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Reduce unused CSS
110 ms · 188 KiBAbout 188 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 110 ms faster on a phone.
19 long tasks on the main thread
19 long tasks block the main thread while loading, the longest for 203 ms. During a long task the page ignores taps.
Legacy JavaScript
9 KiBPolyfills for old browsers add 9 KiB JavaScript that modern phones do not need.
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.
Minify JavaScript
4 KiB4 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 4 ms
4 msYour server sent the HTML in 4 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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.
Time to Interactive: 13.3 s
13.3 sThe page becomes fully interactive after 13.3 s. Good is under 3.8 s.
Speed Index: 7.8 s
7.8 sVisually, the page fills in at 7.8 s (Speed Index). Good is under 3.4 s.
Real-user INP: 264 ms
264 msReal visitors wait 264 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.11
0.11For real visitors the layout shifts by 0.11 (75th percentile). Good is under 0.1.
Total Blocking Time: 445 ms
445 msScripts block taps and scrolling for 445 ms in total while the page loads. Good is under 200 ms.
First Contentful Paint: 2.6 s
2.6 sThe first text or image appears after 2.6 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 2.6 s
2.6 sYour largest element takes 2.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “A raíz de la aparición de avisos falsos sobre oportunidades…”. Most of its time is element render delay (2.4 s).
2 images without width and height
2 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 11% slower for real visitors
+11%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 233 ms to 260 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user LCP: 1.5 s
1.5 sReal visitors wait 1.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 1.4 s
1.4 sReal visitors see the first content after 1.4 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 531 ms
531 msReal visitors wait 531 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 23% faster for real visitors
-23%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 2.4 s to 1.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.023
0.023The layout barely moves while loading (CLS 0.023, good is under 0.1).
Images and page weight
3 images far larger than shown
584 KiB3 images are downloaded at several times the size a phone draws them, for example TR-Testmark_9000015894_EN_CMYK_with-QR-Code.jpg at 1,965 px wide, shown at 300 px. Resized copies would save about 584 KiB.
Page weight: 3.0 MB in 152 requests
3.0 MBYour homepage downloads 3.0 MB in 152 requests on a phone: scripts 1.7 MB (120), images 964 KiB (12) and stylesheets 186 KiB (4). Under 2 MB keeps phones on slow connections fast.
3 images in older formats
3 images (683 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 below the first screen load straight away
1 image further down the page (358 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 0.9 g of CO₂ per visit
0.86 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.86 g of CO₂e: 103.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
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.
ARIA role should be appropriate for the element (2 elements)
ARIA role should be appropriate for the element: 2 elements on the page fail this check, rated minor by axe-core.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (2 elements).
1 checks passed
45 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 49 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 4 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Structured data has 2 problems
Structured data found (Organization, WebPage and WebSite) but with 2 problems, for example “Organization: missing name”.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
259 internal links, 22 external
The homepage links to 259 pages on randstad.com.ar and 22 external pages.
7 checks passed
Meta description: 124 characters
Your meta description is 124 characters: “Conectamos a las personas con las empresas que desarrollarán su potencial. Empleos. Trabajo. Soluciones en Recursos Hum…”.
One H1 headline
Your main headline reads: “¡encontrá el trabajo que buscás!”.
Title: 59 characters
Your title is a healthy 59 characters: “Empleos | Trabajo | Randstad Argentina | Randstad Argentina”.
Canonical URL set
The canonical URL is https://www.randstad.com.ar/.
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 and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://www.randstad.com.ar/sitemaps/sitemap.xml.
AI search readiness
Organization data is thin (0 of 6 facts)
Your Organization JSON-LD is missing name, 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://www.randstad.com.ar/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,249 words), so crawlers that don't run JavaScript still read it.
Other pages
2 linked pages hidden from search
https://www.randstad.com.ar/trabajos/q-tecnologia and https://www.randstad.com.ar/trabajos/q-planta are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.
2 pages share a title
https://www.randstad.com.ar/trabajos/q-ventas and https://www.randstad.com.ar/trabajos/q-salud all use the title “Encontrá trabajos de ventas en Argentina | Randstad Argentina”. Search engines can't tell which page to show for a search, so each competes with the others.
4 pages share a meta description
https://www.randstad.com.ar/candidatos/primer-empleo-buscamos-tu-talento and https://www.randstad.com.ar/candidatos/descarga-randstad-app use the same meta description. A description written for each page earns more clicks.
2 links to non-canonical URLs
Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://www.randstad.com.ar/candidatos/operational, whose canonical is https://www.randstad.com.ar/carreras-laborales-operational. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 122 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.
Every page has a meta description
All 15 pages that loaded have a meta description.
Every page has an H1
Each page we checked has a main headline.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Uncaught Error: Minified React error #418; visit https://reactjs.org/docs/error-decoder.html?invariant=418 for the full…”.
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
2 checks passed
Tap targets are thumb-sized
9 of 10 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
A 16-field form
Your longest form asks for 16 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 492 words of copy
The homepage carries about 492 words of visible text.
3 checks passed
4 calls to action
The homepage has 4 calls to action, for example “contact center y servicio al cliente”.
Social proof on the page
Social proof on the homepage: 1 customer or partner logo and 1 trust badge.
Direct contact links
Visitors can reach you directly: 1 phone link and 0 email links.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads Google Tag Manager (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.
4 cookies set on arrival
4Opening the homepage sets 4 cookies (measured from a US location before any click).
6 other companies contacted
Loading the homepage contacts 6 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: OneTrust
A consent management tool (OneTrust) loads with the page.
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 randstad.com.ar, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- Drupal
- Framework
- React
- Hosting
- AWS
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 39 issues on randstad.com.ar, including 19 speed issues, 2 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.