Website review, no card needed

Jobber logo

getjobber.com website review

Visit site (opens in a new tab)Reviewed 26 October 202642 issues · 75 checks

This review found 42 issues worth fixing on getjobber.com, 17 of them high impact, across 75 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

Read the full growth playbook for Jobber

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Site score

69D

Not ranked: the homepage didn't load normally in this review.

Real-visitor load time (LCP)75th percentile, phones
1.8 s1.5 sMay 9Oct 241.8 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20261.6 s
May 16, 20261.6 s
May 23, 20261.5 s
May 30, 20261.5 s
Jun 6, 20261.5 s
Jun 13, 20261.6 s
Jun 20, 20261.6 s
Jun 27, 20261.6 s
Jul 4, 20261.6 s
Jul 11, 20261.7 s
Jul 18, 20261.7 s
Jul 25, 20261.7 s
Aug 1, 20261.6 s
Aug 8, 20261.5 s
Aug 15, 20261.5 s
Aug 22, 20261.6 s
Aug 29, 20261.6 s
Sep 5, 20261.7 s
Sep 12, 20261.7 s
Sep 19, 20261.7 s
Sep 26, 20261.7 s
Oct 3, 20261.7 s
Oct 10, 20261.7 s
Oct 17, 20261.7 s
Oct 24, 20261.8 s
Real-visitor tap response (INP)75th percentile, phones
139 ms128 msMay 9Oct 24134 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026130 ms
May 16, 2026129 ms
May 23, 2026129 ms
May 30, 2026129 ms
Jun 6, 2026131 ms
Jun 13, 2026134 ms
Jun 20, 2026136 ms
Jun 27, 2026137 ms
Jul 4, 2026138 ms
Jul 11, 2026138 ms
Jul 18, 2026137 ms
Jul 25, 2026136 ms
Aug 1, 2026132 ms
Aug 8, 2026130 ms
Aug 15, 2026129 ms
Aug 22, 2026132 ms
Aug 29, 2026135 ms
Sep 5, 2026137 ms
Sep 12, 2026137 ms
Sep 19, 2026137 ms
Sep 26, 2026137 ms
Oct 3, 2026137 ms
Oct 10, 2026137 ms
Oct 17, 2026136 ms
Oct 24, 2026134 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 getjobber.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. getjobber.com at 0.4 s0.4 s
  2. getjobber.com at 0.9 s0.9 s
  3. getjobber.com at 1.3 s1.3 s
  4. getjobber.com at 1.8 s1.8 s
  5. getjobber.com at 2.2 s2.2 s
  6. getjobber.com at 2.7 s2.7 s
  7. getjobber.com at 3.1 s3.1 s
  8. getjobber.com at 3.6 s3.6 s

Speed

12 to fix33
  • Reduce unused JavaScript

    1.4 s · 1.8 MB

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

  • Main-thread work: 12.7 s

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

  • Intercom adds 1.2 s

    1.2 s

    Intercom costs a phone 1.2 s of main-thread work and 972 KiB 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: 33

    33/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Intercom, Google Tag Manager and Google CDN and others), adding 3.1 MB and 3.9 s of main-thread time.

  • Use efficient cache lifetimes

    350 ms · 912 KiB

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

  • Google Tag Manager adds 972 ms

    972 ms

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

  • 20 long tasks on the main thread

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

  • Google CDN adds 613 ms

    613 ms

    Google CDN costs a phone 613 ms of main-thread work and 734 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.

  • Facebook adds 292 ms

    292 ms

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

  • joshuarms.com adds 287 ms

    287 ms

    joshuarms.com costs a phone 287 ms of main-thread work and 61 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.

  • 1,562 HTML elements

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

  • Improve image delivery

    180 KiB

    6 images could be 180 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Legacy JavaScript

    63 KiB

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

  • Reduce unused CSS

    55 KiB

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

  • 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

    2 KiB

    2 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 136 ms

    136 ms

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

Core Web Vitals

8 to fix100
  • 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: 39.0 s

    39.0 s

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

  • Total Blocking Time: 3.7 s

    3.7 s

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

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

  • Largest Contentful Paint: 7.3 s

    7.3 s

    Your largest element takes 7.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Run a stronger service business From first quote to final p…”.

  • Real-user FCP: 2.0 s

    2.0 s

    Real visitors see the first content after 2.0 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.

  • First Contentful Paint: 2.7 s

    2.7 s

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

  • Tap response (INP) held steady for real visitors

    +4%

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

  • Largest content (LCP) held steady for real visitors

    +9%

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

4 checks passed
  • Real-user LCP: 2.2 s

    2.2 s

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

  • Real-user INP: 146 ms

    146 ms

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

  • Real-user CLS: 0.02

    0.02

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

  • Cumulative Layout Shift: 0.045

    0.045

    The layout barely moves while loading (CLS 0.045, good is under 0.1).

Images and page weight

2 to fix60
  • Page weight: 6.1 MB in 178 requests

    6.1 MB

    Your homepage downloads 6.1 MB in 178 requests on a phone: scripts 4.0 MB (62), images 1.1 MB (30) and other files 482 KiB (71). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    48 KiB

    1 image is downloaded at several times the size a phone draws it, for example image at 1,800 px wide, shown at 342 px. Resized copies would save about 48 KiB.

  • 1 image in older formats

    1 image (42 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.7 g of CO₂ per visit

    1.73 g

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

1 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

4 to fixGoogle 9495
  • Certain ARIA roles must contain particular children (1 element)

    Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

  • Heading levels should only increase by one (3 elements)

    Heading levels should only increase by one: 3 elements on the page fail this check, rated moderate by axe-core.

  • 8 links without text

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

1 checks passed
  • 44 automated accessibility rules passed

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

SEO

10 to fixGoogle 8539
  • Page is set to noindex

    The robots meta tag says “noindex,nofollow”: Google is told not to list this page at all.

  • No meta description

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

  • No H1 headline

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

  • Title is short (16 characters)

    Your title is only 16 characters: “Just a moment...”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

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

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • No social preview image

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

  • Only 0 internal links

    The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • 5 links with vague text

    5 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • No X (Twitter) card tag

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

2 checks passed
  • 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://getjobber.com/sitemap_index.xml.

AI search readiness

100
1 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.

Best practices

1 to fixGoogle 9293
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “The Content Security Policy directive 'upgrade-insecure-requests' is ignored when delivered in a report-only policy.”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Content security policy”).

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix33
  • Homepage answers HTTP 403

    Your homepage answered with HTTP 403, so visitors and search engines may see an error page.

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

  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • 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 form on the homepage

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

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

    The homepage carries about 705 words of visible text.

1 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Pricing” and “Start Free Trial”.

Privacy and tracking

  • 13 trackers load before any consent

    13

    Before a visitor clicks anything, the page loads Amazon Ads, Amplitude, Criteo, Google Ads and Google Analytics and 8 mores (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.

  • 40 cookies set on arrival

    40

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

  • 56 other companies contacted

    Loading the homepage contacts 56 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 getjobber.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
Next.js
Hosting
Cloudflare

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 42 issues on getjobber.com, including 20 speed issues, 10 SEO issues and 5 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