Website review, no card needed
calforex.com website review
Visit site (opens in a new tab)Reviewed 23 October 202622 issues · 72 checks
This review found 22 issues worth fixing on calforex.com, 7 of them high impact, across 72 checks. The most urgent: improve image delivery. 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
86BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 910 ms |
| May 9, 2026 | 892 ms |
| May 16, 2026 | 887 ms |
| May 23, 2026 | 893 ms |
| May 30, 2026 | 897 ms |
| Jun 6, 2026 | 894 ms |
| Jun 13, 2026 | 885 ms |
| Jun 20, 2026 | 876 ms |
| Jun 27, 2026 | 863 ms |
| Jul 4, 2026 | 870 ms |
| Jul 11, 2026 | 873 ms |
| Jul 18, 2026 | 874 ms |
| Jul 25, 2026 | 857 ms |
| Aug 1, 2026 | 848 ms |
| Aug 8, 2026 | 832 ms |
| Aug 15, 2026 | 826 ms |
| Aug 22, 2026 | 845 ms |
| Aug 29, 2026 | 857 ms |
| Sep 5, 2026 | 879 ms |
| Sep 12, 2026 | 893 ms |
| Sep 19, 2026 | 890 ms |
| Sep 26, 2026 | 892 ms |
| Oct 3, 2026 | 889 ms |
| Oct 10, 2026 | 896 ms |
| Oct 17, 2026 | 918 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 87 ms |
| May 9, 2026 | 87 ms |
| May 16, 2026 | 87 ms |
| May 23, 2026 | 87 ms |
| May 30, 2026 | 87 ms |
| Jun 6, 2026 | 87 ms |
| Jun 13, 2026 | 88 ms |
| Jun 20, 2026 | 89 ms |
| Jun 27, 2026 | 88 ms |
| Jul 4, 2026 | 88 ms |
| Jul 11, 2026 | 88 ms |
| Jul 18, 2026 | 87 ms |
| Jul 25, 2026 | 88 ms |
| Aug 1, 2026 | 89 ms |
| Aug 8, 2026 | 91 ms |
| Aug 15, 2026 | 89 ms |
| Aug 22, 2026 | 89 ms |
| Aug 29, 2026 | 89 ms |
| Sep 5, 2026 | 88 ms |
| Sep 12, 2026 | 89 ms |
| Sep 19, 2026 | 89 ms |
| Sep 26, 2026 | 88 ms |
| Oct 3, 2026 | 89 ms |
| Oct 10, 2026 | 90 ms |
| Oct 17, 2026 | 91 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
Improve image delivery
1.9 s · 497 KiB11 images could be 497 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.9 s faster on a phone.
Reduce unused JavaScript
900 ms · 137 KiBAbout 137 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 900 ms faster on a phone.
Mobile performance score: 64
64/100Your mobile performance score is 64 (desktop: 96). Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
600 ms14 files block the first paint until they finish downloading. Deferring or inlining them could save about 600 ms.
5 third-party services on the page
5 third-party services load with your homepage (Google Maps, Google Tag Manager and elfsight.com and others), adding 1.1 MB and 314 ms of main-thread time.
Use efficient cache lifetimes
300 ms · 111 KiB3 files are served with short cache lifetimes, so returning visitors download them again (111 KiB).
Google Maps adds 192 ms
192 msGoogle Maps costs a phone 192 ms of main-thread work and 808 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.
2,013 HTML elements
The page has 2,013 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
4 long tasks on the main thread
4 long tasks block the main thread while loading, the longest for 67 ms. During a long task the page ignores taps.
Phones get a much slower page than desktops
Desktop scores 96 but mobile only 64. A gap that wide usually means heavy scripts and images that hit phones hardest.
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, 470 ms of it running JavaScript. That is comfortably low.
Server response: 8 ms
8 msYour server sent the HTML in 8 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 9.0 s
9.0 sYour largest element takes 9.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Bank Beating Rates Right At Your Fingertips! We provide the…”.
Time to Interactive: 9.0 s
9.0 sThe page becomes fully interactive after 9.0 s. Good is under 3.8 s.
Speed Index: 6.3 s
6.3 sVisually, the page fills in at 6.3 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.2 s
3.2 sThe first text or image appears after 3.2 s on a phone. Good is under 1.8 s.
Tap response (INP) held steady for real visitors
+4%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 87 ms to 91 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+1%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 0.9 s to 0.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
8 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 0.9 s
0.9 sReal visitors wait 0.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 105 ms
105 msReal visitors wait 105 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.
Real-user FCP: 0.9 s
0.9 sReal visitors see the first content after 0.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 440 ms
440 msReal visitors wait 440 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 36 ms
36 msScripts block the page for only 36 ms while loading. Good is under 200 ms.
Images and page weight
1 image in older formats
1 image (55 KiB) is 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.
4 images below the first screen load straight away
4 images further down the page (124 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 0.5 g of CO₂ per visit
0.49 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.49 g of CO₂e: 59.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Page weight: 1.7 MB in 59 requests
1.7 MBYour homepage downloads 1.7 MB in 59 requests on a phone: images 1.0 MB (17), scripts 524 KiB (16) and fonts 119 KiB (4). That is a lean page.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
6 links without text
6 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h2 → h6), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 6 images in the HTML carry an alt attribute.
44 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 46 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 2 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
2 H1 headlines
There are 2 <h1> headlines (“Bank Beating Rates Right At Your Fingertips!” and “Read testimonials from customers who have experie…”). One clear main headline is easier for people and search engines.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
106 internal links, 63 external
The homepage links to 106 pages on calforex.com and 63 external pages.
6 checks passed
Meta description: 156 characters
Your meta description is 156 characters: “We provide the best rates on foreign exchange while maintaining the widest selection of foreign currencies available in…”.
Title: 44 characters
Your title is a healthy 44 characters: “Home - Calforex Best Currency Exchange Rates”.
Canonical URL set
The canonical URL is https://www.calforex.com/en/.
Structured data in place
Structured data found: Article, ImageObject, Organization, Person and WebPage.
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.calforex.com/sitemap_index.xml.
AI search readiness
Organization data is thin (2 of 6 facts)
Your Organization JSON-LD is missing url, 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.
No llms.txt
There is no https://www.calforex.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 (963 words), so crawlers that don't run JavaScript still read it.
Other pages
14 pages without a meta description
https://www.calforex.com/fr, https://www.calforex.com/en/locations, https://www.calforex.com/en/locations/calgary-ab-downtown, https://www.calforex.com/en/locations/calgary-ab-chinook-centre, https://www.calforex.com/en/locations/edmonton-ab-southgate-mall and https://www.calforex.com/en/locations/edmonton-ab-west-ed-mall and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://www.calforex.com/en/locations/montreal-qc-rue-peel has 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 66 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.
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 15 pages that loaded have a <title>.
Best practices
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 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.
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 505 words of copy
The homepage carries about 505 words of visible text.
3 checks passed
9 calls to action
The homepage has 9 calls to action, for example “Reserve Cash Online”, “Contact” and “Reserve Cash”.
18 short forms
18 short forms (4 fields at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Analytics.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Google Analytics and Google Tag Manager (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.
4 cookies set on arrival
4Opening the homepage sets 4 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.
8 other companies contacted
Loading the homepage contacts 8 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 calforex.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
- The footer still says © 2025.
Stack
- CMS
- WordPress
- Analytics
- Google Analytics
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 22 issues on calforex.com, including 12 speed issues, 2 SEO issues 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.