Website review, no card needed

upshift.work logo

upshift.work website review

Visit site (opens in a new tab)Reviewed 31 October 202638 issues · 79 checks

This review found 38 issues worth fixing on upshift.work, 16 of them high impact, across 79 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
4.0 s3.7 sMay 9Oct 243.8 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20263.8 s
May 16, 20263.8 s
May 23, 20263.9 s
May 30, 20263.9 s
Jun 6, 20263.9 s
Jun 13, 20263.9 s
Jun 20, 20263.9 s
Jun 27, 20263.9 s
Jul 4, 20263.9 s
Jul 11, 20263.8 s
Jul 18, 20263.8 s
Jul 25, 20263.7 s
Aug 1, 20263.8 s
Aug 8, 20263.8 s
Aug 15, 20263.9 s
Aug 22, 20263.9 s
Aug 29, 20264.0 s
Sep 5, 20264.0 s
Sep 12, 20264.0 s
Sep 19, 20264.0 s
Sep 26, 20264.0 s
Oct 3, 20263.9 s
Oct 10, 20263.9 s
Oct 17, 20263.9 s
Oct 24, 20263.8 s
Real-visitor tap response (INP)75th percentile, phones
968 ms684 msMay 9Oct 24726 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026914 ms
May 16, 2026927 ms
May 23, 2026935 ms
May 30, 2026928 ms
Jun 6, 2026903 ms
Jun 13, 2026876 ms
Jun 20, 2026839 ms
Jun 27, 2026848 ms
Jul 4, 2026856 ms
Jul 11, 2026862 ms
Jul 18, 2026851 ms
Jul 25, 2026841 ms
Aug 1, 2026845 ms
Aug 8, 2026812 ms
Aug 15, 2026835 ms
Aug 22, 2026843 ms
Aug 29, 2026837 ms
Sep 5, 2026858 ms
Sep 12, 2026849 ms
Sep 19, 2026837 ms
Sep 26, 2026799 ms
Oct 3, 2026760 ms
Oct 10, 2026739 ms
Oct 17, 2026717 ms
Oct 24, 2026726 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 upshift.work (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. upshift.work at 0.4 s0.4 s
  2. upshift.work at 0.8 s0.8 s
  3. upshift.work at 1.2 s1.2 s
  4. upshift.work at 1.6 s1.6 s
  5. upshift.work at 2.0 s2.0 s
  6. upshift.work at 2.4 s2.4 s
  7. upshift.work at 2.8 s2.8 s
  8. upshift.work at 3.3 s3.3 s

Speed

10 to fix35
  • Reduce unused JavaScript

    2.4 s · 989 KiB

    About 989 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.4 s faster on a phone.

  • Render-blocking requests

    2.5 s

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

  • Mobile performance score: 35

    35/100

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

  • Main-thread work: 4.1 s

    A phone's processor spends 4.1 s on main-thread work while loading, 3.0 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 (Google Tag Manager, Facebook and heatmap.com and others), adding 1.3 MB and 1.3 s of main-thread time.

  • 13 long tasks on the main thread

    13 long tasks block the main thread while loading, the longest for 1.4 s. During a long task the page ignores taps.

  • Google Tag Manager adds 866 ms

    866 ms

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

    750 ms · 129 KiB

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

  • Use efficient cache lifetimes

    350 ms · 460 KiB

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

  • Minify JavaScript

    600 ms · 136 KiB

    136 KiB could be saved by minifying JavaScript.

  • Legacy JavaScript

    56 KiB

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

  • Improve image delivery

    54 KiB

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

  • Font display

    50 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 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: 23 ms

    23 ms

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

Core Web Vitals

8 to fix33
  • 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.

  • Largest Contentful Paint: 10.7 s

    10.7 s

    Your largest element takes 10.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Upshift app showing available shifts”.

  • Time to Interactive: 19.3 s

    19.3 s

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

  • Total Blocking Time: 2.0 s

    2.0 s

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

  • Speed Index: 7.2 s

    7.2 s

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

  • First Contentful Paint: 3.2 s

    3.2 s

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

  • Real-user LCP: 3.0 s

    3.0 s

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

  • Real-user INP: 210 ms

    210 ms

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

  • Largest content (LCP) held steady for real visitors

    +1%

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

5 checks passed
  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 1.7 s

    1.7 s

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

  • Real-user TTFB: 741 ms

    741 ms

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

  • Tap response (INP) got 22% faster for real visitors

    -22%

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

  • Cumulative Layout Shift: 0.008

    0.008

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

Images and page weight

1 to fix85
  • Page weight: 2.5 MB in 114 requests

    2.5 MB

    Your homepage downloads 2.5 MB in 114 requests on a phone: scripts 2.0 MB (50), fonts 187 KiB (5) and stylesheets 166 KiB (13). Under 2 MB keeps phones on slow connections fast.

  • 2 images in older formats

    2 images (92 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.

  • About 0.7 g of CO₂ per visit

    0.72 g

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

2 checks passed
  • Images load when needed

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

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

5 to fixGoogle 8792
  • 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.

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • Zoom is disabled

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

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

2 checks passed
  • Every image has alt text

    All 9 images in the HTML carry an alt attribute.

  • 31 automated accessibility rules passed

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

SEO

4 to fixGoogle 10078
  • No H1 headline

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

  • Title is long (77 characters)

    Your title is 77 characters, so Google will cut it off around 60: “We Make Work Better- for People and Businesses | Staffing Redefined | Upshift”.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • Only 4 internal links

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

5 checks passed
  • Meta description: 154 characters

    Your meta description is 154 characters: “We have revolutionized the old-school staffing model. Since 2016, Upshift has been connecting flexible job seekers with…”.

  • Canonical URL set

    The canonical URL is https://upshift.work/.

  • Structured data in place

    Structured data found: BreadcrumbList, WebPage and WebSite.

  • 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://upshift.work/sitemap_index.xml.

AI search readiness

1 to fix83
  • 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://upshift.work/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.

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.

Other pages

1 to fix95
  • 1 page without an H1

    https://upshift.work/for-people has no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 internal pages checked

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

6 checks passed
  • Linked pages load

    All 2 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 2 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 2 pages that loaded have a <title>.

Best practices

3 to fixGoogle 7773
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=343036388&Ver=2&mid=a650bbf8-52dd-4c36-963d-59805a923bd4&bo=1&sid=46569390d52d11f1b9aadd15b0ef1329&vid=4656c050d52d11f1a7e7739eb2950fb3&vids=1&msclkid=N&pi=918639831&l.

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).

  • 2 JavaScript errors while loading

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

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix43
  • 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.

  • 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 direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

  • Only about 58 words

    The homepage has only about 58 words of visible text; thin pages give Google and first-time buyers little to go on.

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

2 checks passed
  • 1 short form

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

  • Analytics in place

    Analytics detected: Google Tag Manager and Segment.

Privacy and tracking

  • 8 trackers load before any consent

    8

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and HubSpot and 3 mores (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

  • 24 cookies set on arrival

    24

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

  • 49 other companies contacted

    Loading the homepage contacts 49 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • Consent tool: HubSpot cookie banner

    A consent management tool (HubSpot cookie banner) 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 upshift.work, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
WordPress
Framework
jQuery
Analytics
Google Tag Manager | Segment
Hosting
WordPress.com

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 38 issues on upshift.work, including 18 speed issues, 4 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