Website review, no card needed
gsr.io website review
Visit site (opens in a new tab)Reviewed 1 November 202630 issues · 84 checks
This review found 30 issues worth fixing on gsr.io, 10 of them high impact, across 84 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
81BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 2.2 s |
| May 16, 2026 | 2.2 s |
| May 23, 2026 | 2.3 s |
| May 30, 2026 | 2.3 s |
| Jun 6, 2026 | 2.4 s |
| Jun 13, 2026 | 2.5 s |
| Jun 20, 2026 | 3.4 s |
| Jun 27, 2026 | 3.9 s |
| Jul 4, 2026 | 4.0 s |
| Jul 11, 2026 | 4.0 s |
| Jul 18, 2026 | 3.5 s |
| Jul 25, 2026 | 3.4 s |
| Aug 1, 2026 | 3.4 s |
| Aug 8, 2026 | 3.4 s |
| Aug 15, 2026 | 3.7 s |
| Aug 22, 2026 | 4.0 s |
| Aug 29, 2026 | 3.9 s |
| Sep 5, 2026 | 4.0 s |
| Sep 12, 2026 | 3.9 s |
| Sep 19, 2026 | 3.8 s |
| Sep 26, 2026 | 3.7 s |
| Oct 3, 2026 | 3.8 s |
| Oct 10, 2026 | 3.8 s |
| Oct 17, 2026 | 3.9 s |
| Oct 24, 2026 | 4.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 204 ms |
| May 16, 2026 | 196 ms |
| May 23, 2026 | 185 ms |
| May 30, 2026 | 184 ms |
| Jun 6, 2026 | 190 ms |
| Jun 13, 2026 | 178 ms |
| Jun 20, 2026 | 186 ms |
| Jun 27, 2026 | 166 ms |
| Jul 4, 2026 | 161 ms |
| Jul 11, 2026 | 157 ms |
| Jul 18, 2026 | 136 ms |
| Jul 25, 2026 | 142 ms |
| Aug 1, 2026 | 127 ms |
| Aug 8, 2026 | 130 ms |
| Aug 15, 2026 | 130 ms |
| Aug 22, 2026 | 128 ms |
| Aug 29, 2026 | 127 ms |
| Sep 5, 2026 | 126 ms |
| Sep 12, 2026 | 132 ms |
| Sep 19, 2026 | 127 ms |
| Sep 26, 2026 | 129 ms |
| Oct 3, 2026 | 142 ms |
| Oct 10, 2026 | 142 ms |
| Oct 17, 2026 | 157 ms |
| Oct 24, 2026 | 175 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
Speed
Render-blocking requests
2.1 s19 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.1 s.
Main-thread work: 5.3 s
A phone's processor spends 5.3 s on main-thread work while loading, 2.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Reduce unused JavaScript
770 ms · 693 KiBAbout 693 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 770 ms faster on a phone.
5 third-party services on the page
5 third-party services load with your homepage (Google CDN, Optanon and Other Google APIs/SDKs and others), adding 1.8 MB and 1.3 s of main-thread time.
Mobile performance score: 53
53/100Your mobile performance score is 53. Pages that score under 90 lose visitors before the first paint.
Google CDN adds 870 ms
870 msGoogle CDN costs a phone 870 ms of main-thread work and 1.1 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.
Use efficient cache lifetimes
400 ms · 66 KiB7 files are served with short cache lifetimes, so returning visitors download them again (66 KiB).
craft.cloud adds 101 ms
101 mscraft.cloud costs a phone 101 ms of main-thread work and 425 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.
15 long tasks on the main thread
15 long tasks block the main thread while loading, the longest for 236 ms. During a long task the page ignores taps.
Minify JavaScript
150 ms · 31 KiB31 KiB could be saved by minifying JavaScript.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Reduce unused CSS
18 KiBAbout 18 KiB of CSS is downloaded but never applied on this page.
Improve image delivery
13 KiB1 image could be 13 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Legacy JavaScript
9 KiBPolyfills for old browsers add 9 KiB JavaScript that modern phones do not need.
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: 4 ms
4 msYour server sent the HTML in 4 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 LCP: 4.6 s
4.6 sReal visitors wait 4.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 4.2 s
4.2 sReal visitors see the first content after 4.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 2.4 s
2.4 sReal visitors wait 2.4 s for your server to start answering (75th percentile). Good is under 800 ms.
Time to Interactive: 12.4 s
12.4 sThe page becomes fully interactive after 12.4 s. Good is under 3.8 s.
Largest Contentful Paint: 5.2 s
5.2 sYour largest element takes 5.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Crypto’s Capital Markets Partner”. Most of its time is element render delay (2.7 s).
Total Blocking Time: 878 ms
878 msScripts block taps and scrolling for 878 ms in total while the page loads. Good is under 200 ms.
Largest content (LCP) got 82% slower for real visitors
+82%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.2 s to 4.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Speed Index: 5.6 s
5.6 sVisually, the page fills in at 5.6 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.3 s
2.3 sThe first text or image appears after 2.3 s on a phone. Good is under 1.8 s.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
4 checks passed
Real-user INP: 168 ms
168 msReal visitors wait 168 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Tap response (INP) got 17% faster for real visitors
-17%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 204 ms to 175 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 2.2 MB in 81 requests
2.2 MBYour homepage downloads 2.2 MB in 81 requests on a phone: scripts 1.3 MB (28), other files 392 KiB (10) and images 212 KiB (15). Under 2 MB keeps phones on slow connections fast.
About 0.6 g of CO₂ per visit
0.63 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.63 g of CO₂e: 75.4 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
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.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
2 checks passed
Every image has alt text
All 38 images in the HTML carry an alt attribute.
48 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 49 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 1 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 2 problems
Structured data found (BreadcrumbList, Organization and WebPage) but with 2 problems, for example “Organization: missing name”.
53 internal links, 18 external
The homepage links to 53 pages on gsr.io and 18 external pages.
7 checks passed
Meta description: 122 characters
Your meta description is 122 characters: “GSR is Crypto’s Capital Markets Partner. We specialize in providing trading solutions, market making, and risk manageme…”.
One H1 headline
Your main headline reads: “Crypto’s Capital Markets Partner”.
Title: 54 characters
Your title is a healthy 54 characters: “Crypto Trading Firm & Liquidity Provider | GSR Markets”.
Canonical URL set
The canonical URL is https://www.gsr.io/.
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.gsr.io/sitemaps-1-sitemap.xml.
AI search readiness
Organization data is thin (0 of 6 facts)
Your Organization JSON-LD is missing name, url, logo, sameAs (social profiles), 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 (796 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.gsr.io/llms.txt (7 KiB, 66 links), a plain-text guide to the site for AI tools.
Other pages
4 pages share a meta description
https://www.gsr.io/who-we-serve, https://www.gsr.io/services/markets, https://www.gsr.io/insights/max-eddie-faq-2026-2-2 and https://www.gsr.io/insights/gsr-expands-regulated-footprint-for-the-onchain-future-of-finance use the same meta description. A description written for each page earns more clicks.
1 page slow to respond
https://www.gsr.io/contact-us took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 26 found) and read each the way a search engine does.
7 checks passed
Linked pages load
9 pages of 15 loaded without an error (the rest turned automated requests away).
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 9 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
Every page has an H1
Each page we checked has a main headline.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 9 pages that loaded have a <title>.
Best practices
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Executing inline event handler violates the following Content Security Policy directive 'script-src 'self' 'nonce-oKjS9…”.
2 checks passed
Tap targets are thumb-sized
23 of 24 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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 opening hours
The homepage shows no opening hours. If customers visit or call, show when.
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 694 words of copy
The homepage carries about 694 words of visible text.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Get in touch”.
9 calls to action
The homepage has 9 calls to action, for example “Contact us”, “Get in touch” and “Subscribe”.
1 short form
A short form (7 fields at most) is right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Analytics, Microsoft Clarity, Segment and LinkedIn Insight.
Privacy and tracking
3 cookies set on arrival
3Opening the homepage sets 3 cookies (measured from a US location before any click).
7 other companies contacted
Loading the homepage contacts 7 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
2 checks passed
Consent tool: OneTrust
A consent management tool (OneTrust) loads with the page.
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 gsr.io, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Analytics
- Google Analytics | Segment | Microsoft Clarity
- Hosting
- Cloudflare
Hiring
- Hiring
- 5 open roles
- Teams
- Engineering (1), Markets (1), OTC (1), Quantitative Development (1)
- Job board
- greenhouse
- Careers page
- www.gsr.io/careers (opens in a new tab)
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 30 issues on gsr.io, including 19 speed issues, 1 SEO issue 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.