Website review, no card needed
changeinvest.com website review
Visit site (opens in a new tab)Reviewed 20 October 202632 issues · 83 checks
This review found 32 issues worth fixing on changeinvest.com, 7 of them high impact, across 83 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
88BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 2.6 s |
| May 9, 2026 | 2.6 s |
| May 16, 2026 | 1.9 s |
| May 23, 2026 | 1.9 s |
| May 30, 2026 | 1.9 s |
| Jun 6, 2026 | 1.8 s |
| Jun 13, 2026 | 2.2 s |
| Jun 20, 2026 | 2.4 s |
| Jun 27, 2026 | 2.6 s |
| Jul 4, 2026 | 2.6 s |
| Jul 11, 2026 | 2.9 s |
| Jul 18, 2026 | 3.0 s |
| Jul 25, 2026 | 3.1 s |
| Aug 1, 2026 | 3.0 s |
| Aug 8, 2026 | 2.9 s |
| Aug 15, 2026 | 2.8 s |
| Aug 22, 2026 | 2.7 s |
| Aug 29, 2026 | 2.7 s |
| Sep 5, 2026 | 2.7 s |
| Sep 12, 2026 | 2.7 s |
| Sep 19, 2026 | 2.6 s |
| Sep 26, 2026 | 2.7 s |
| Oct 3, 2026 | 2.8 s |
| Oct 10, 2026 | 2.8 s |
| Oct 17, 2026 | 2.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 109 ms |
| May 9, 2026 | 111 ms |
| May 16, 2026 | 112 ms |
| May 23, 2026 | 112 ms |
| May 30, 2026 | 111 ms |
| Jun 6, 2026 | 111 ms |
| Jun 13, 2026 | 115 ms |
| Jun 20, 2026 | 114 ms |
| Jun 27, 2026 | 112 ms |
| Jul 4, 2026 | 111 ms |
| Jul 11, 2026 | 104 ms |
| Jul 18, 2026 | 106 ms |
| Jul 25, 2026 | 107 ms |
| Aug 1, 2026 | 105 ms |
| Aug 8, 2026 | 106 ms |
| Aug 15, 2026 | 106 ms |
| Aug 22, 2026 | 106 ms |
| Aug 29, 2026 | 106 ms |
| Sep 5, 2026 | 112 ms |
| Sep 12, 2026 | 116 ms |
| Sep 19, 2026 | 113 ms |
| Sep 26, 2026 | 113 ms |
| Oct 3, 2026 | 119 ms |
| Oct 10, 2026 | 113 ms |
| Oct 17, 2026 | 122 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
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Render-blocking requests
2.5 s3 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.5 s.
Improve image delivery
450 ms · 555 KiB16 images could be 555 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.
Mobile performance score: 59
59/100Your mobile performance score is 59 (desktop: 70). Pages that score under 90 lose visitors before the first paint.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Facebook and website-files.com and others), adding 1.8 MB and 401 ms of main-thread time.
Reduce unused JavaScript
447 KiBAbout 447 KiB of JavaScript is downloaded but never used on this page.
Reduce unused CSS
300 ms · 80 KiBAbout 80 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
website-files.com adds 78 ms
78 mswebsite-files.com costs a phone 78 ms of main-thread work and 1.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.
Google Tag Manager adds 144 ms
144 msGoogle Tag Manager costs a phone 144 ms of main-thread work and 352 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.
Use efficient cache lifetimes
155 KiB4 files are served with short cache lifetimes, so returning visitors download them again (155 KiB).
6 long tasks on the main thread
6 long tasks block the main thread while loading, the longest for 99 ms. During a long task the page ignores taps.
Minify JavaScript
34 KiB34 KiB could be saved by minifying JavaScript.
Legacy JavaScript
19 KiBPolyfills for old browsers add 19 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.
2 checks passed
Main-thread work: 1.1 s
A phone's processor spends 1.1 s on main-thread work while loading, 503 ms of it running JavaScript. That is comfortably low.
Server response: 3 ms
3 msYour server sent the HTML in 3 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.
Largest Contentful Paint: 5.6 s
5.6 sYour largest element takes 5.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 10.5 s
10.5 sThe page becomes fully interactive after 10.5 s. Good is under 3.8 s.
First Contentful Paint: 3.5 s
3.5 sThe first text or image appears after 3.5 s on a phone. Good is under 1.8 s.
Real-user FCP: 1.9 s
1.9 sReal visitors see the first content after 1.9 s (75th percentile). Good is under 1.8 s.
77 images without width and height
77 images have no width and height attributes, so the layout jumps as each one loads.
Cumulative Layout Shift: 0.237
0.237The layout shifts by 0.237 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Speed Index: 3.5 s
3.5 sVisually, the page fills in at 3.5 s (Speed Index). Good is under 3.4 s.
Tap response (INP) held steady for real visitors
+7%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 109 ms to 122 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+7%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.6 s to 2.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user LCP: 2.3 s
2.3 sReal visitors wait 2.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 120 ms
120 msReal visitors wait 120 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
Real-user TTFB: 629 ms
629 msReal visitors wait 629 ms for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 103 ms
103 msScripts block the page for only 103 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 2.2 MB in 92 requests
2.2 MBYour homepage downloads 2.2 MB in 92 requests on a phone: images 959 KiB (46), scripts 928 KiB (20) and fonts 230 KiB (6). Under 2 MB keeps phones on slow connections fast.
2 images in older formats
2 images (87 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.6 g of CO₂ per visit
0.62 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.62 g of CO₂e: 74.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
31 text elements with low contrast
31 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
All page content should be contained by landmarks (108 elements)
All page content should be contained by landmarks: 108 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
9 links without text
9 visible links have no text or label, so screen readers cannot say where they go.
2 checks passed
Every image has alt text
All 127 images in the HTML carry an alt attribute.
36 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 40 WCAG 2.2 A/AA and best-practice rules on the phone render: 36 passed and 4 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
54 internal links, 21 external
The homepage links to 54 pages on changeinvest.com and 21 external pages.
8 checks passed
Meta description: 148 characters
Your meta description is 148 characters: “Buy 140+ cryptocurrencies and trade 360+ CFDs on stocks, forex, indices and commodities. Easy to use, low fees, MiCA re…”.
One H1 headline
Your main headline reads: “all-in-one trading platform.”.
Title: 54 characters
Your title is a healthy 54 characters: “Change | Trade Crypto & CFDs on Stocks, Forex, Indices”.
Canonical URL set
The canonical URL is https://www.changeinvest.com/.
Structured data in place
Structured data found: WebSite.
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.changeinvest.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.
No llms.txt
There is no https://www.changeinvest.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 (1,670 words), so crawlers that don't run JavaScript still read it.
Other pages
1 linked page hidden from search
https://www.changeinvest.com/careers-old is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
2 pages share a title
https://www.changeinvest.com/about and https://www.changeinvest.com/about-us all use the title “About Change | EU Regulated Crypto Exchange Since 2018”. Search engines can't tell which page to show for a search, so each competes with the others.
2 pages without a meta description
https://www.changeinvest.com/prices and https://www.changeinvest.com/careers-old have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages share a meta description
https://www.changeinvest.com/about and https://www.changeinvest.com/about-us use the same meta description. A description written for each page earns more clicks.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.changeinvest.com/about-us, whose canonical is https://www.changeinvest.com/about. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
1 page without an H1
https://www.changeinvest.com/prices has no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://www.changeinvest.com/prices has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 22 found) and read each the way a search engine does.
2 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Adjust.waitForAttribution is not a function”.
2 distorted images
2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
Missing source maps
Large scripts ship without source maps.
2 checks passed
Tap targets are thumb-sized
12 of 12 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.
About 967 words of copy
The homepage carries about 967 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: “Download the app”.
11 calls to action
The homepage has 11 calls to action, for example “Download the app”, “Pricing” and “Contact us”.
1 short form
A short form (3 fields at most) is right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics, Meta Pixel and Segment.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Reddit Pixel and 1 more (measured from a US location before any click). A consent tool (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.
7 cookies set on arrival
7Opening the homepage sets 7 cookies (measured from a US location before any click).
22 other companies contacted
Loading the homepage contacts 22 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: CookieYes
A consent management tool (CookieYes) 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 changeinvest.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
- Analytics
- Google Analytics | Google Tag Manager | Segment
Hiring
- Hiring
- 3 open roles
- Teams
- Petitions (Change.org) (3)
- Job board
- ashby
- Careers page
- careers.changeinvest.com (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 32 issues on changeinvest.com, including 16 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.