Website review, no card needed

rocketjobs.pl logo

rocketjobs.pl website review

Visit site (opens in a new tab)Reviewed 21 October 202647 issues · 85 checks

This review found 47 issues worth fixing on rocketjobs.pl, 19 of them high impact, across 85 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.8 s1.7 sMay 2Oct 172.6 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20261.9 s
May 9, 20261.9 s
May 16, 20262.0 s
May 23, 20262.2 s
May 30, 20262.3 s
Jun 6, 20262.4 s
Jun 13, 20262.3 s
Jun 20, 20262.2 s
Jun 27, 20262.1 s
Jul 4, 20262.1 s
Jul 11, 20262.1 s
Jul 18, 20262.2 s
Jul 25, 20262.3 s
Aug 1, 20262.3 s
Aug 8, 20262.3 s
Aug 15, 20262.3 s
Aug 22, 20262.2 s
Aug 29, 20262.1 s
Sep 5, 20262.1 s
Sep 12, 20262.1 s
Sep 19, 20262.2 s
Sep 26, 20262.4 s
Oct 3, 20262.6 s
Oct 10, 20262.6 s
Oct 17, 20262.6 s
Real-visitor tap response (INP)75th percentile, phones
624 ms388 msMay 2Oct 17430 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026578 ms
May 9, 2026562 ms
May 16, 2026544 ms
May 23, 2026554 ms
May 30, 2026570 ms
Jun 6, 2026584 ms
Jun 13, 2026597 ms
Jun 20, 2026579 ms
Jun 27, 2026562 ms
Jul 4, 2026553 ms
Jul 11, 2026544 ms
Jul 18, 2026543 ms
Jul 25, 2026536 ms
Aug 1, 2026526 ms
Aug 8, 2026524 ms
Aug 15, 2026535 ms
Aug 22, 2026560 ms
Aug 29, 2026560 ms
Sep 5, 2026525 ms
Sep 12, 2026473 ms
Sep 19, 2026434 ms
Sep 26, 2026420 ms
Oct 3, 2026415 ms
Oct 10, 2026416 ms
Oct 17, 2026430 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 rocketjobs.pl (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. rocketjobs.pl at 1.1 s1.1 s
  2. rocketjobs.pl at 2.2 s2.2 s
  3. rocketjobs.pl at 3.3 s3.3 s
  4. rocketjobs.pl at 4.4 s4.4 s
  5. rocketjobs.pl at 5.5 s5.5 s
  6. rocketjobs.pl at 6.6 s6.6 s
  7. rocketjobs.pl at 7.7 s7.7 s
  8. rocketjobs.pl at 8.8 s8.8 s

Speed

10 to fix42
  • Reduce unused JavaScript

    7.2 s · 1.3 MB

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

  • Use efficient cache lifetimes

    2.2 s · 986 KiB

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

  • Mobile performance score: 42

    42/100

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

  • Main-thread work: 6.2 s

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

  • Improve image delivery

    3.4 MB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Cookie-Script.com, Facebook and TikTok and others), adding 1.2 MB and 774 ms of main-thread time.

  • Legacy JavaScript

    450 ms · 90 KiB

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

  • 20 long tasks on the main thread

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

  • 2,903 HTML elements

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

  • LiveChat adds 58 ms

    58 ms

    LiveChat costs a phone 58 ms of main-thread work and 368 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.

  • Reduce unused CSS

    150 ms · 46 KiB

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

  • Render-blocking requests

    100 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 100 ms.

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

    50 ms

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

Core Web Vitals

12 to fix0
  • 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.0 s

    4.0 s

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

  • Real-user INP: 777 ms

    777 ms

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

  • Largest Contentful Paint: 38.6 s

    38.6 s

    Your largest element takes 38.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Nasza strona wykorzystuje pliki cookies do realizacji usług…”.

  • Speed Index: 17.4 s

    17.4 s

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

  • Time to Interactive: 40.2 s

    40.2 s

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

  • Total Blocking Time: 781 ms

    781 ms

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

  • Real-user CLS: 0.12

    0.12

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

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

    +41%

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

  • Real-user FCP: 2.7 s

    2.7 s

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

  • Real-user TTFB: 1.6 s

    1.6 s

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

  • Cumulative Layout Shift: 0.104

    0.104

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

2 checks passed
  • Tap response (INP) got 26% faster for real visitors

    -26%

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

  • First Contentful Paint: 1.7 s

    1.7 s

    The first text or image appears after 1.7 s, inside the 1.8 s “good” threshold.

Images and page weight

5 to fix18
  • Page weight: 8.0 MB in 208 requests

    8.0 MB

    Your homepage downloads 8.0 MB in 208 requests on a phone: images 4.1 MB (67), scripts 3.2 MB (82) and fonts 412 KiB (12). Under 2 MB keeps phones on slow connections fast.

  • 16 images far larger than shown

    2.1 MB

    16 images are downloaded at several times the size a phone draws them, for example hf_20261013_112335_b3ef7eab-7342-49b5-ac91-1b1b976d83c5-770x at 770 px wide, shown at 96 px. Resized copies would save about 2.1 MB.

  • 2 images over 500 KB

    2 images weigh 1.2 MB together. On a phone connection a single image that size takes seconds.

  • 6 images in older formats

    6 images (1.4 MB) 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.

  • 5 images below the first screen load straight away

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

  • About 2.3 g of CO₂ per visit

    2.27 g

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

Accessibility

6 to fixGoogle 8990
  • 6 text elements with low contrast

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

  • 9 images without alt text

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

  • All page content should be contained by landmarks (4 elements)

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

  • Zoom is disabled

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

  • 14 links without text

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

  • 3 form fields without a label

    3 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • Headings skip levels

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

1 checks passed
  • 33 automated accessibility rules passed

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

SEO

3 to fixGoogle 10084
  • Title is short (21 characters)

    Your title is only 21 characters: “Praca - rocketjobs.pl”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Meta description is short (28 characters)

    Your meta description is only 28 characters: “Twój portal z ofertami pracy”. 70 to 160 characters is enough to sell the click.

  • Structured data has 1 problem

    Structured data found (Organization and WebSite) but with 1 problem, for example “WebSite: missing name”.

  • 267 internal links, 10 external

    The homepage links to 267 pages on rocketjobs.pl and 10 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “Zdobądź pracę u najlepszych.”.

  • Canonical URL set

    The canonical URL is https://rocketjobs.pl/.

  • 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://rocketjobs.pl/sitemaps/active-jobs.xml.

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing logo, 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.

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

  • llms.txt published

    The site publishes https://rocketjobs.pl/llms.txt (4 KiB, 25 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix93
  • 2 pages share a meta description

    https://rocketjobs.pl/oferty-pracy/wszystkie-lokalizacje and https://rocketjobs.pl/kalkulator-wynagrodzen use the same meta description. A description written for each page earns more clicks.

  • 3 pages without an H1

    https://rocketjobs.pl/kalkulator-wynagrodzen, https://rocketjobs.pl/brands and https://rocketjobs.pl/blog have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://rocketjobs.pl/brands has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 199 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

3 to fixGoogle 5476
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=343165599&tm=gtm002&Ver=2&mid=8a453e3d-874b-499c-b021-5d7026cff818&bo=1&sid=3c7f0c80cd3211f19b34676c765f4ef2&vid=3c7f23d0cd3211f1afa7a98f483f8f4e&vids=1&msclkid=N&pi=9.

  • 1 third-party cookie

    1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://cdn.maptiler.com/maptiler-sdk-js/v3.0.1/maptiler-sdk.css' from origin 'https://roc…”.

  • Missing source maps

    Large scripts ship without source maps.

  • Browser-reported issues

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

2 checks passed
  • Tap targets are thumb-sized

    128 of 135 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix50
  • 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 calls to action

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

  • Thin social proof

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

  • No direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach 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 1,170 words of copy

    The homepage carries about 1,170 words of visible text.

2 checks passed
  • 2 short forms

    2 short forms (3 fields at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

1 to fix
  • 9 trackers load before any consent

    9

    Before a visitor clicks anything, the page loads Criteo, Google Ads, Google Analytics, Google Tag Manager and LinkedIn Insight and 4 mores (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.

  • 14 cookies set on arrival

    14

    Opening the homepage sets 14 cookies, 6 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.

  • 34 other companies contacted

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 47 issues on rocketjobs.pl, including 22 speed issues, 3 SEO issues and 4 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

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