Website review, no card needed
gorgias.com website review
Visit site (opens in a new tab)Reviewed 17 November 202636 issues · 85 checks
This review found 36 issues worth fixing on gorgias.com, 16 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.
Read the full growth playbook for Gorgias
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
73CClosest competitors among SaaS websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 4.5 s |
| Jun 6, 2026 | 4.7 s |
| Jun 13, 2026 | 4.9 s |
| Jun 20, 2026 | 5.0 s |
| Jun 27, 2026 | 5.1 s |
| Jul 4, 2026 | 5.0 s |
| Jul 11, 2026 | 4.7 s |
| Jul 18, 2026 | 4.5 s |
| Jul 25, 2026 | 4.2 s |
| Aug 1, 2026 | 4.3 s |
| Aug 8, 2026 | 4.2 s |
| Aug 15, 2026 | 4.2 s |
| Aug 22, 2026 | 4.3 s |
| Aug 29, 2026 | 4.3 s |
| Sep 5, 2026 | 4.7 s |
| Sep 12, 2026 | 4.7 s |
| Sep 19, 2026 | 4.7 s |
| Sep 26, 2026 | 4.7 s |
| Oct 3, 2026 | 4.7 s |
| Oct 10, 2026 | 4.6 s |
| Oct 17, 2026 | 4.6 s |
| Oct 24, 2026 | 5.1 s |
| Oct 31, 2026 | 5.2 s |
| Nov 7, 2026 | 5.2 s |
| Nov 14, 2026 | 5.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 257 ms |
| Jun 6, 2026 | 243 ms |
| Jun 13, 2026 | 245 ms |
| Jun 20, 2026 | 254 ms |
| Jun 27, 2026 | 240 ms |
| Jul 4, 2026 | 238 ms |
| Jul 11, 2026 | 230 ms |
| Jul 18, 2026 | 217 ms |
| Jul 25, 2026 | 214 ms |
| Aug 1, 2026 | 228 ms |
| Aug 8, 2026 | 233 ms |
| Aug 15, 2026 | 238 ms |
| Aug 22, 2026 | 236 ms |
| Aug 29, 2026 | 218 ms |
| Sep 5, 2026 | 227 ms |
| Sep 12, 2026 | 217 ms |
| Sep 19, 2026 | 228 ms |
| Sep 26, 2026 | 240 ms |
| Oct 3, 2026 | 238 ms |
| Oct 10, 2026 | 254 ms |
| Oct 17, 2026 | 257 ms |
| Oct 24, 2026 | 246 ms |
| Oct 31, 2026 | 236 ms |
| Nov 7, 2026 | 222 ms |
| Nov 14, 2026 | 213 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
How it loaded on a phone
1.0 s
2.1 s
3.1 s
4.2 s
5.2 s
6.2 s
7.3 s
8.3 s
Speed
Reduce unused JavaScript
7.2 s · 1.4 MBAbout 1.4 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.
Wistia adds 1.1 s
1.1 sWistia costs a phone 1.1 s of main-thread work and 1.5 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.
Render-blocking requests
1.1 s6 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.
Mobile performance score: 46
46/100Your mobile performance score is 46. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 6.8 s
A phone's processor spends 6.8 s on main-thread work while loading, 4.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
3,646 HTML elements
The page has 3,646 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Use efficient cache lifetimes
550 ms · 5.2 MB60 files are served with short cache lifetimes, so returning visitors download them again (5.2 MB).
8 third-party services on the page
8 third-party services load with your homepage (Wistia, website-files.com and Facebook and others), adding 8.7 MB and 2.5 s of main-thread time.
website-files.com adds 712 ms
712 mswebsite-files.com costs a phone 712 ms of main-thread work and 6.2 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.
16 long tasks on the main thread
16 long tasks block the main thread while loading, the longest for 160 ms. During a long task the page ignores taps.
Minify JavaScript
29 KiB29 KiB could be saved by minifying JavaScript.
Reduce unused CSS
29 KiBAbout 29 KiB of CSS is downloaded but never applied on this page.
Improve image delivery
24 KiB2 images could be 24 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Legacy JavaScript
22 KiBPolyfills for old browsers add 22 KiB JavaScript that modern phones do not need.
Duplicated JavaScript
10 KiB10 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: 24 ms
24 msYour server sent the HTML in 24 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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 FCP: 5.1 s
5.1 sReal visitors see the first content after 5.1 s (75th percentile). Good is under 1.8 s.
First Contentful Paint: 7.9 s
7.9 sThe first text or image appears after 7.9 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 22.6 s
22.6 sYour largest element takes 22.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Time to Interactive: 33.1 s
33.1 sThe page becomes fully interactive after 33.1 s. Good is under 3.8 s.
Speed Index: 14.7 s
14.7 sVisually, the page fills in at 14.7 s (Speed Index). Good is under 3.4 s.
Real-user LCP: 3.6 s
3.6 sReal visitors wait 3.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 345 ms
345 msReal visitors wait 345 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Total Blocking Time: 389 ms
389 msScripts block taps and scrolling for 389 ms in total while the page loads. 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.
Largest content (LCP) got 12% slower for real visitors
+12%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 4.5 s to 5.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user CLS: 0.07
0.07For real visitors the layout shifts by 0.07 (75th percentile). Good is under 0.1.
Real-user TTFB: 452 ms
452 msReal visitors wait 452 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 13% faster for real visitors
-13%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 257 ms to 213 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.05
0.05The layout barely moves while loading (CLS 0.05, good is under 0.1).
Images and page weight
Page weight: 10.2 MB in 254 requests
10.2 MBYour homepage downloads 10.2 MB in 254 requests on a phone: media 4.3 MB (2), scripts 3.6 MB (123) and images 882 KiB (49). Under 2 MB keeps phones on slow connections fast.
About 2.9 g of CO₂ per visit
2.89 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.89 g of CO₂e: 347.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
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
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.
Elements must only use permitted ARIA attributes (35 elements)
Elements must only use permitted ARIA attributes: 35 elements on the page fail this check, rated serious by axe-core.
Contentinfo landmark should not be contained in another landmark (1 element)
Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.
Document should not have more than one contentinfo landmark (1 element)
Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 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.
Elements marked as presentational should be consistently ignored (1 element)
Elements marked as presentational should be consistently ignored: 1 element on the page fails this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 193 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 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 8 failed. 5 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Structured data has 1 problem
Structured data found (WebPage) but with 1 problem, for example “WebPage: url is not an absolute URL ("/")”.
155 internal links, 20 external
The homepage links to 155 pages on gorgias.com and 20 external pages.
7 checks passed
Meta description: 150 characters
Your meta description is 150 characters: “Drive more sales and automate support with AI Agent, Helpdesk integrated to your stack, Chat, FAQ and more. Trusted by …”.
One H1 headline
Your main headline reads: “Deliver the best customer experience”.
Title: 54 characters
Your title is a healthy 54 characters: “The Conversational AI platform for Ecommerce | Gorgias”.
Canonical URL set
The canonical URL is https://www.gorgias.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.
XML sitemap found
Your XML sitemap is reachable at https://www.gorgias.com/sitemap.xml.
AI search readiness
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.
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 (954 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.gorgias.com/llms.txt (7 KiB, 49 links), a plain-text guide to the site for AI tools.
Other pages
5 linked pages hidden from search
https://www.gorgias.com/industry/clothing-apparel, https://www.gorgias.com/industry/subscriptions, https://www.gorgias.com/industry/beauty-cosmetics, https://www.gorgias.com/industry/health-wellness and https://www.gorgias.com/industry/home-garden are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.
5 pages without an H1
https://www.gorgias.com/product-launch/fall-launch, https://www.gorgias.com/demo, https://www.gorgias.com/ai-agent, https://www.gorgias.com/gaia and https://www.gorgias.com/product-tour 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 84 found) and read each the way a search engine does.
5 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.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
2 broken images
2 images failed to load on a phone, for example https://rdcdn.com/rt?aid=22184&e=1&img=1.
1 small tap target
1 of 5 tappable elements near the top of the page is smaller than 24 px, hard to hit with a thumb.
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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,260 words of copy
The homepage carries about 1,260 words of visible text.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Book a demo” and “Discover pricing”.
11 calls to action
The homepage has 11 calls to action, for example “Pricing”, “Book a demo” and “Sign up free”.
1 short form
A short form (1 field at most) is right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 8 testimonial or review blocks, 3 customer or partner logos, a star rating and 7 trust badges.
Analytics in place
Analytics detected: HubSpot and Segment.
Privacy and tracking
9 trackers load before any consent
9Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, LinkedIn Insight, Meta Pixel and Microsoft Ads 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.
19 cookies set on arrival
19Opening the homepage sets 19 cookies, 2 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.
59 other companies contacted
Loading the homepage contacts 59 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 gorgias.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
- Tailwind CSS
- Analytics
- Segment
- Hosting
- Webflow
Hiring
- Hiring
- 12 open roles
- Teams
- Customer Success (7), Marketing (4), Engineering (1)
- Job board
- ashby
- Careers page
- www.gorgias.com/careers (opens in a new tab)
Company
- Headquarters
- San Francisco
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 36 issues on gorgias.com, including 19 speed issues, 1 SEO issue 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.