Website review, no card needed

golance.com logo

golance.com website review

Visit site (opens in a new tab)Reviewed 3 November 202646 issues · 90 checks

This review found 46 issues worth fixing on golance.com, 18 of them high impact, across 90 checks. The most urgent: page weight: 39.0 MB in 162 requests. 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
6.8 s4.8 sMay 16Oct 315.2 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20265.0 s
May 23, 20265.1 s
May 30, 20265.0 s
Jun 6, 20265.0 s
Jun 13, 20265.1 s
Jun 20, 20265.1 s
Jun 27, 20265.1 s
Jul 4, 20265.1 s
Jul 11, 20265.1 s
Jul 18, 20265.0 s
Jul 25, 20265.0 s
Aug 1, 20265.3 s
Aug 8, 20265.5 s
Aug 15, 20265.9 s
Aug 22, 20266.1 s
Aug 29, 20266.5 s
Sep 5, 20266.6 s
Sep 12, 20266.6 s
Sep 19, 20266.4 s
Sep 26, 20266.4 s
Oct 3, 20266.3 s
Oct 10, 20266.1 s
Oct 17, 20266.0 s
Oct 24, 20265.5 s
Oct 31, 20265.2 s
Real-visitor tap response (INP)75th percentile, phones
371 ms267 msMay 16Oct 31314 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026279 ms
May 23, 2026294 ms
May 30, 2026294 ms
Jun 6, 2026289 ms
Jun 13, 2026296 ms
Jun 20, 2026291 ms
Jun 27, 2026304 ms
Jul 4, 2026307 ms
Jul 11, 2026313 ms
Jul 18, 2026311 ms
Jul 25, 2026308 ms
Aug 1, 2026313 ms
Aug 8, 2026320 ms
Aug 15, 2026336 ms
Aug 22, 2026338 ms
Aug 29, 2026349 ms
Sep 5, 2026359 ms
Sep 12, 2026349 ms
Sep 19, 2026345 ms
Sep 26, 2026342 ms
Oct 3, 2026327 ms
Oct 10, 2026327 ms
Oct 17, 2026331 ms
Oct 24, 2026320 ms
Oct 31, 2026314 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 golance.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. golance.com at 0.5 s0.5 s
  2. golance.com at 1.1 s1.1 s
  3. golance.com at 1.6 s1.6 s
  4. golance.com at 2.2 s2.2 s
  5. golance.com at 2.7 s2.7 s
  6. golance.com at 3.2 s3.2 s
  7. golance.com at 3.8 s3.8 s
  8. golance.com at 4.3 s4.3 s

Speed

13 to fix38
  • Mobile performance score: 38

    38/100

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

  • Main-thread work: 4.7 s

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

  • 3,385 HTML elements

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

  • Use efficient cache lifetimes

    600 ms · 7.2 MB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Wistia and Facebook and others), adding 19.0 MB and 1.7 s of main-thread time.

  • Improve image delivery

    3.3 MB

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

  • website-files.com adds 164 ms

    164 ms

    website-files.com costs a phone 164 ms of main-thread work and 17.6 MB 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 JavaScript

    600 ms · 1.0 MB

    About 1.0 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 600 ms faster on a phone.

  • Render-blocking requests

    900 ms

    2 files block the first paint until they finish downloading. Deferring or inlining them could save about 900 ms.

  • Reduce unused CSS

    600 ms · 131 KiB

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

  • Google Tag Manager adds 604 ms

    604 ms

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

  • Wistia adds 492 ms

    492 ms

    Wistia costs a phone 492 ms of main-thread work and 414 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.

  • 16 long tasks on the main thread

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

  • Legacy JavaScript

    13 KiB

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

  • Duplicated JavaScript

    8 KiB

    8 KiB JavaScript is shipped twice across bundles.

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

    77 ms

    Your server sent the HTML in 77 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: 5.2 s

    5.2 s

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

  • Real-user CLS: 0.34

    0.34

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

  • Real-user FCP: 4.3 s

    4.3 s

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

  • Real-user TTFB: 1.9 s

    1.9 s

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

  • Largest Contentful Paint: 42.8 s

    42.8 s

    Your largest element takes 42.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • Time to Interactive: 43.8 s

    43.8 s

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

  • Speed Index: 10.3 s

    10.3 s

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

  • Total Blocking Time: 1.1 s

    1.1 s

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

  • First Contentful Paint: 3.0 s

    3.0 s

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

  • Real-user INP: 301 ms

    301 ms

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

  • 4 images without width and height

    4 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-10-31, real Chrome visitors' tap response (inp) went from 279 ms to 314 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) held steady for real visitors

    +6%

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

1 checks passed
  • Cumulative Layout Shift: 0.052

    0.052

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

Images and page weight

3 to fix45
  • Page weight: 39.0 MB in 162 requests

    39.0 MB

    Your homepage downloads 39.0 MB in 162 requests on a phone: media 26.1 MB (20), images 10.3 MB (41) and scripts 1.6 MB (40). Under 2 MB keeps phones on slow connections fast.

  • 4 images over 500 KB

    4 images weigh 5.0 MB together. On a phone connection a single image that size takes seconds.

  • 7 images in older formats

    7 images (5.6 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.

  • About 11.1 g of CO₂ per visit

    11.07 g

    By the Sustainable Web Design model, a visit to your homepage emits about 11.07 g of CO₂e: 1328.1 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 9193
  • 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.

  • Scrollable region must have keyboard access (1 element)

    Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

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

  • 3 form fields without a label

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

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • Headings skip levels

    Headings skip levels (h1 → h4, h1 → h4 and h1 → h4), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 120 images in the HTML carry an alt attribute.

  • 47 automated accessibility rules passed

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

SEO

1 to fixGoogle 10095
  • 11 H1 headlines

    There are 11 <h1> headlines (“Hire for Skills and Cultural Fit”, “Hire for Skills and Cultural Fit” and “Hire for Skills and Cultural Fit”). One clear main headline is easier for people and search engines.

  • 107 internal links, 24 external

    The homepage links to 107 pages on golance.com and 24 external pages.

7 checks passed
  • Meta description: 153 characters

    Your meta description is 153 characters: “goLance helps you quickly find and hire developers, content creators, digital marketers and more. Click to search our m…”.

  • Title: 48 characters

    Your title is a healthy 48 characters: “Hire Talent With goLance's Freelance Marketplace”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: EmploymentAgency.

  • 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://golance.com/sitemap.xml.

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

Other pages

4 to fix81
  • 2 pages share a title

    https://golance.com/hire/freelancer/evan.fisher and https://golance.com/hire all use the title “goLance”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 10 pages without a meta description

    https://golance.com/global-payroll, https://golance.com/for-freelancers, https://golance.com/contracts, https://golance.com/manage-team-projects, https://golance.com/post-jobs and https://golance.com/approve-invoices and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://golance.com/hire/freelancer/evan.fisher and https://golance.com/hire use the same meta description. A description written for each page earns more clicks.

  • 2 pages without an H1

    https://golance.com/hire/freelancer/evan.fisher and https://golance.com/hire 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 32 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.

  • Canonical URLs point to themselves

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

  • 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 9276
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=97054877&tm=gtm002&Ver=2&mid=1f96a700-265e-4fd1-a627-6d2ecfc32b6b&bo=1&sid=e37cda80d74611f1a96bd954b246f1ee&vid=e37cf9c0d74611f1ae95730fcbd286bb&vids=1&msclkid=N&pi=91.

  • 5 JavaScript errors while loading

    5 errors were logged to the browser console while the page loaded, for example “Identifier 'loopStart' has already been declared”.

  • 17 distorted images

    17 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

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

3 to fix83
  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • No phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • 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 map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

    The homepage carries about 958 words of visible text.

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Sign Up”.

  • 18 calls to action

    The homepage has 18 calls to action, for example “Sign Up”, “Get Started” and “Sarah’s PTO Request”.

  • 9 short forms

    9 short forms (1 field at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: a star rating and 3 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics, Meta Pixel, Microsoft Clarity and Segment.

  • Opening hours shown

    Your opening hours are on the homepage.

Privacy and tracking

1 to fix
  • 7 trackers load before any consent

    7

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Ads and 2 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.

  • 13 cookies set on arrival

    13

    Opening the homepage sets 13 cookies (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.

  • 36 other companies contacted

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

Upkeep, stack and company

Stack

CMS
Webflow
Framework
Vue.js
E-commerce
Shopify
Analytics
Google Analytics | Google Tag Manager | Segment | Microsoft Clarity
Hosting
AWS

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 46 issues on golance.com, including 25 speed issues, 1 SEO issue 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

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