Website review, no card needed

hoytrabajas.com logo

hoytrabajas.com website review

Visit site (opens in a new tab)Reviewed 23 October 202641 issues · 81 checks

This review found 41 issues worth fixing on hoytrabajas.com, 22 of them high impact, across 81 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
5.3 s3.7 sMay 2Oct 174.3 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20265.0 s
May 9, 20265.0 s
May 16, 20265.0 s
May 23, 20265.0 s
May 30, 20264.9 s
Jun 6, 20264.7 s
Jun 13, 20264.4 s
Jun 20, 20264.1 s
Jun 27, 20264.0 s
Jul 4, 20264.0 s
Jul 11, 20264.1 s
Jul 18, 20263.9 s
Jul 25, 20263.9 s
Aug 1, 20264.0 s
Aug 8, 20264.3 s
Aug 15, 20264.8 s
Aug 22, 20265.1 s
Aug 29, 20265.1 s
Sep 5, 20264.9 s
Sep 12, 20264.5 s
Sep 19, 20264.5 s
Sep 26, 20264.5 s
Oct 3, 20264.6 s
Oct 10, 20264.4 s
Oct 17, 20264.3 s
Real-visitor tap response (INP)75th percentile, phones
186 ms134 msMay 2Oct 17140 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026143 ms
May 9, 2026144 ms
May 16, 2026144 ms
May 23, 2026146 ms
May 30, 2026156 ms
Jun 6, 2026158 ms
Jun 13, 2026162 ms
Jun 20, 2026168 ms
Jun 27, 2026166 ms
Jul 4, 2026167 ms
Jul 11, 2026180 ms
Jul 18, 2026164 ms
Jul 25, 2026161 ms
Aug 1, 2026161 ms
Aug 8, 2026158 ms
Aug 15, 2026161 ms
Aug 22, 2026162 ms
Aug 29, 2026162 ms
Sep 5, 2026169 ms
Sep 12, 2026153 ms
Sep 19, 2026150 ms
Sep 26, 2026154 ms
Oct 3, 2026144 ms
Oct 10, 2026141 ms
Oct 17, 2026140 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 hoytrabajas.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. hoytrabajas.com at 0.9 s0.9 s
  2. hoytrabajas.com at 1.8 s1.8 s
  3. hoytrabajas.com at 2.7 s2.7 s
  4. hoytrabajas.com at 3.6 s3.6 s
  5. hoytrabajas.com at 4.5 s4.5 s
  6. hoytrabajas.com at 5.4 s5.4 s
  7. hoytrabajas.com at 6.3 s6.3 s
  8. hoytrabajas.com at 7.2 s7.2 s

Speed

11 to fix26
  • Reduce unused JavaScript

    11.5 s · 1.5 MB

    About 1.5 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 11.5 s faster on a phone.

  • Use efficient cache lifetimes

    5.5 s · 2.5 MB

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

  • Render-blocking requests

    2.1 s

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

  • Minify JavaScript

    1.5 s · 278 KiB

    278 KiB could be saved by minifying JavaScript.

  • YouTube adds 1.2 s

    1.2 s

    YouTube costs a phone 1.2 s of main-thread work and 1.9 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Mobile performance score: 26

    26/100

    Your mobile performance score is 26 (desktop: 48). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Main-thread work: 4.4 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (YouTube, Google Tag Manager and JSDelivr CDN and others), adding 2.3 MB and 1.3 s of main-thread time.

  • Improve image delivery

    1.0 MB

    4 images could be 1.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 15 long tasks on the main thread

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

  • Reduce unused CSS

    300 ms · 82 KiB

    About 82 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.

  • Document request latency

    69 KiB

    The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

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

    108 ms

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

Core Web Vitals

11 to fix67
  • 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 LCP: 4.3 s

    4.3 s

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

  • Real-user FCP: 3.7 s

    3.7 s

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

  • Real-user TTFB: 2.9 s

    2.9 s

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

  • Largest Contentful Paint: 25.7 s

    25.7 s

    Your largest element takes 25.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Revisa los datos de las ofertas laborales”.

  • Time to Interactive: 26.1 s

    26.1 s

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

  • Speed Index: 13.3 s

    13.3 s

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

  • Total Blocking Time: 1.2 s

    1.2 s

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

  • First Contentful Paint: 3.3 s

    3.3 s

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

  • 40 images without width and height

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

  • Cumulative Layout Shift: 0.199

    0.199

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

  • Tap response (INP) held steady for real visitors

    -2%

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

3 checks passed
  • Real-user INP: 137 ms

    137 ms

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

  • Real-user CLS: 0.01

    0.01

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

  • Largest content (LCP) got 12% faster for real visitors

    -12%

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

Images and page weight

5 to fix18
  • Page weight: 4.9 MB in 87 requests

    4.9 MB

    Your homepage downloads 4.9 MB in 87 requests on a phone: scripts 2.8 MB (15), images 1.6 MB (42) and HTML 244 KiB (3). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    logo_trabajo-2325935bd4a2338bd0c22ec02abc862d47df6f062759021 weighs 868 KiB. On a phone connection a single image that size takes seconds.

  • 1 image far larger than shown

    862 KiB

    1 image is downloaded at several times the size a phone draws it, for example logo_trabajo-2325935bd4a2338bd0c22ec02abc862d47df6f062759021 at 2,274 px wide, shown at 65 px. Resized copies would save about 862 KiB.

  • 8 images below the first screen load straight away

    8 images further down the page (1.1 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 1 image in older formats

    1 image (868 KiB) is 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.4 g of CO₂ per visit

    1.39 g

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

Accessibility

6 to fixGoogle 6689
  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Form elements should have a visible label (1 element)

    Form elements should have a visible label: 1 element on the page fails this check, rated serious by axe-core.

  • 68 images without alt text

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

  • Zoom is disabled

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

  • 5 links without text

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

1 checks passed
  • 34 automated accessibility rules passed

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

SEO

2 to fixGoogle 9292
  • No structured data

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

  • No XML sitemap

    No XML sitemap at http://www.hoytrabajas.com/sitemap.xml, so Google discovers your pages only by following links.

  • 64 internal links, 15 external

    The homepage links to 64 pages on hoytrabajas.com and 15 external pages.

6 checks passed
  • Meta description: 147 characters

    Your meta description is 147 characters: “Trabajos hoy, miles de empleos te esperan en HoyTrabajas, tu buscador de empleo en Colombia.🥇Vinculados al Servicio Pú…”.

  • One H1 headline

    Your main headline reads: “Busca trabajo en Colombia”.

  • Title: 57 characters

    Your title is a healthy 57 characters: “Trabajos Hoy en Colombia | Buscador de Empleo HoyTrabajas”.

  • Canonical URL set

    The canonical URL is https://hoytrabajas.com/.

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

AI search readiness

1 to fix88
  • No Organization structured data

    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.

  • No llms.txt

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

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,018 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix95
  • 12 pages without an H1

    https://hoytrabajas.com/ofertas-empleo-colombia, https://hoytrabajas.com/ofertas-empleo-colombia/bogota, https://hoytrabajas.com/ofertas-empleo-colombia/medellin, https://hoytrabajas.com/ofertas-empleo-colombia/cali, https://hoytrabajas.com/ofertas-empleo-colombia/trabajo-call-center-agente-servicio-cliente-cobranza-bilingue and https://hoytrabajas.com/ofertas-empleo-colombia/trabajo-seguridad-privada-guarda-vigilante-escolta and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

6 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • 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

2 to fixGoogle 7391
  • 5 third-party cookies

    5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • 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 404 ()”.

  • Browser-reported issues

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

2 checks passed
  • Tap targets are thumb-sized

    18 of 19 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix90
  • Thin social proof

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

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

    The homepage carries about 587 words of visible text.

4 checks passed
  • Clear next step on the first screen

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

  • 2 calls to action

    The homepage has 2 calls to action, for example “Call Center” and “Trabajos de Call Center”.

  • 1 short form

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

  • Analytics in place

    Analytics detected: Google Analytics.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads Google Ads and 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, 1 of them by other companies (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.

  • 12 other companies contacted

    Loading the homepage contacts 12 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 hoytrabajas.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
Tailwind CSS
Analytics
Google Analytics

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 41 issues on hoytrabajas.com, including 22 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