Website review, no card needed
crosscall.com website review
Visit site (opens in a new tab)Reviewed 6 November 202643 issues · 72 checks
This review found 43 issues worth fixing on crosscall.com, 17 of them high impact, across 72 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
68D- #103,443 of 117,610 reviewed websitesbeats 10%
- #62,424 of 66,923 online storesbeats 5%
- #57,571 of 61,018 Shopify storesbeats 5%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 3.3 s |
| May 23, 2026 | 3.4 s |
| May 30, 2026 | 3.4 s |
| Jun 6, 2026 | 3.4 s |
| Jun 13, 2026 | 3.5 s |
| Jun 20, 2026 | 3.5 s |
| Jun 27, 2026 | 3.6 s |
| Jul 4, 2026 | 3.8 s |
| Jul 11, 2026 | 4.0 s |
| Jul 18, 2026 | 4.1 s |
| Jul 25, 2026 | 4.1 s |
| Aug 1, 2026 | 4.2 s |
| Aug 8, 2026 | 4.4 s |
| Aug 15, 2026 | 4.5 s |
| Aug 22, 2026 | 4.4 s |
| Aug 29, 2026 | 4.2 s |
| Sep 5, 2026 | 3.8 s |
| Sep 12, 2026 | 3.7 s |
| Sep 19, 2026 | 3.7 s |
| Sep 26, 2026 | 3.8 s |
| Oct 3, 2026 | 3.9 s |
| Oct 10, 2026 | 4.1 s |
| Oct 17, 2026 | 4.2 s |
| Oct 24, 2026 | 4.2 s |
| Oct 31, 2026 | 4.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 279 ms |
| May 23, 2026 | 271 ms |
| May 30, 2026 | 279 ms |
| Jun 6, 2026 | 278 ms |
| Jun 13, 2026 | 276 ms |
| Jun 20, 2026 | 266 ms |
| Jun 27, 2026 | 261 ms |
| Jul 4, 2026 | 259 ms |
| Jul 11, 2026 | 267 ms |
| Jul 18, 2026 | 273 ms |
| Jul 25, 2026 | 272 ms |
| Aug 1, 2026 | 276 ms |
| Aug 8, 2026 | 274 ms |
| Aug 15, 2026 | 274 ms |
| Aug 22, 2026 | 279 ms |
| Aug 29, 2026 | 300 ms |
| Sep 5, 2026 | 320 ms |
| Sep 12, 2026 | 344 ms |
| Sep 19, 2026 | 360 ms |
| Sep 26, 2026 | 340 ms |
| Oct 3, 2026 | 329 ms |
| Oct 10, 2026 | 312 ms |
| Oct 17, 2026 | 300 ms |
| Oct 24, 2026 | 296 ms |
| Oct 31, 2026 | 287 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.2 s
1.6 s
2.0 s
2.4 s
2.8 s
3.2 s
Speed
Render-blocking requests
1.1 s5 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.
Main-thread work: 6.6 s
A phone's processor spends 6.6 s on main-thread work while loading, 3.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
3,516 HTML elements
The page has 3,516 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
8 third-party services on the page
8 third-party services load with your homepage (Shopify, Kameleoon and Yotpo and others), adding 1.1 MB and 1.1 s of main-thread time.
Mobile performance score: 50
50/100Your mobile performance score is 50. Pages that score under 90 lose visitors before the first paint.
Use efficient cache lifetimes
350 ms · 647 KiB16 files are served with short cache lifetimes, so returning visitors download them again (647 KiB).
Reduce unused JavaScript
300 ms · 494 KiBAbout 494 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.
Shopify adds 487 ms
487 msShopify costs a phone 487 ms of main-thread work and 656 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.
Reduce unused CSS
300 ms · 58 KiBAbout 58 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 331 ms. During a long task the page ignores taps.
Improve image delivery
164 KiB6 images could be 164 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Legacy JavaScript
63 KiBPolyfills for old browsers add 63 KiB JavaScript that modern phones do not need.
Minify JavaScript
32 KiB32 KiB could be saved by minifying JavaScript.
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: 60 ms
60 msYour server sent the HTML in 60 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.1 s
4.1 sReal visitors wait 4.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Time to Interactive: 17.9 s
17.9 sThe page becomes fully interactive after 17.9 s. Good is under 3.8 s.
Largest Contentful Paint: 5.3 s
5.3 sYour largest element takes 5.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Performance you can trust”.
Total Blocking Time: 888 ms
888 msScripts block taps and scrolling for 888 ms in total while the page loads. Good is under 200 ms.
Real-user INP: 286 ms
286 msReal visitors wait 286 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Largest content (LCP) got 25% slower for real visitors
+25%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 3.3 s to 4.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 2.7 s
2.7 sReal visitors see the first content after 2.7 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 814 ms
814 msReal visitors wait 814 ms for your server to start answering (75th percentile). Good is under 800 ms.
Speed Index: 5.8 s
5.8 sVisually, the page fills in at 5.8 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.9 s
2.9 sThe first text or image appears after 2.9 s on a phone. Good is under 1.8 s.
Tap response (INP) held steady for real visitors
+6%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 279 ms to 287 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0.003
0.003The layout barely moves while loading (CLS 0.003, good is under 0.1).
Images and page weight
Page weight: 5.7 MB in 339 requests
5.7 MBYour homepage downloads 5.7 MB in 339 requests on a phone: media 2.3 MB (1), scripts 1.8 MB (165) and other files 885 KiB (131). Under 2 MB keeps phones on slow connections fast.
About 1.6 g of CO₂ per visit
1.61 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.61 g of CO₂e: 193.6 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
2 buttons without a name
2 buttons have no accessible name, so screen readers announce just “button”.
Images must have alternative text (2 elements)
Images must have alternative text: 2 elements on the page fail this check, rated critical by axe-core.
7 text elements with low contrast
7 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Scrollable region must have keyboard access (2 elements)
Scrollable region must have keyboard access: 2 elements on the page fail this check, rated serious by axe-core.
All page content should be contained by landmarks (18 elements)
All page content should be contained by landmarks: 18 elements on the page fail this check, rated moderate by axe-core.
Heading levels should only increase by one (1 element)
Heading levels should only increase by one: 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.
1 checks passed
52 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 58 WCAG 2.2 A/AA and best-practice rules on the phone render: 52 passed and 6 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is long (83 characters)
Your title is 83 characters, so Google will cut it off around 60: “CROSSCALL - Rugged Smartphones & Push-to-Talk Devices for Professionals – Crosscall”.
Meta description is long (205 characters)
Your meta description is 205 characters; Google truncates after about 160, so the end of your pitch is cut.
No robots.txt
There is no robots.txt at crosscall.com/robots.txt, the first file search crawlers ask for.
Only 0 internal links
The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.
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.
4 checks passed
Canonical URL set
The canonical URL is https://www.crosscall.com/en-us.
Structured data in place
Structured data found: Organization and WebSite.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
XML sitemap found
Your XML sitemap is reachable at https://www.crosscall.com/sitemap.xml.
AI search readiness
Most text only appears after JavaScript runs
0%A phone browser shows 702 words, but the HTML your server sends has only 0. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing logo, 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.crosscall.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.
Best practices
21 small tap targets
21 of 48 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “[Regios Discounts] [USER ERROR] To display discounts on product pages, you need to create an automatic product discount…”.
Missing source maps
Large scripts ship without source maps.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
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 form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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 702 words of copy
The homepage carries about 702 words of visible text.
2 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Contact us” and “BUY”.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager and Klaviyo (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.
24 cookies set on arrival
24Opening the homepage sets 24 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.
30 other companies contacted
Loading the homepage contacts 30 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 crosscall.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Apps on your store
Your storefront loads 11 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Intelligems A B Testing · Geo Pro Geolocation · T Lab Ai Translate · Regios Discounts · Klaviyo Email Marketing Sms · Addingwell · Join Stories · Powerful Form Builder · Easylocation · digitaloceanspaces.com · bogos.io
Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info
Upkeep, stack and company
Stack
- E-commerce
- Shopify
- Analytics
- Google Tag Manager
- Hosting
- Shopify
Company
- Employees
- 170
- Founded
- 2009
- Headquarters
- Aix-en-Provence
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 43 issues on crosscall.com, including 21 speed issues, 6 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.