Website review, no card needed
apxor.com website review
Visit site (opens in a new tab)Reviewed 24 October 202636 issues · 77 checks
This review found 36 issues worth fixing on apxor.com, 13 of them high impact, across 77 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
71CClosest competitors among SaaS websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 2.6 s |
| Jun 20, 2026 | 1.9 s |
| Jul 4, 2026 | 1.8 s |
| Jul 25, 2026 | 2.1 s |
| Aug 1, 2026 | 2.2 s |
| Aug 8, 2026 | 2.2 s |
| Aug 15, 2026 | 2.4 s |
| Aug 22, 2026 | 2.5 s |
| Aug 29, 2026 | 2.7 s |
| Oct 10, 2026 | 2.2 s |
| Oct 17, 2026 | 2.4 s |
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
Improve image delivery
1.6 s · 3.7 MB15 images could be 3.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.6 s faster on a phone.
Render-blocking requests
4.8 s2 files block the first paint until they finish downloading. Deferring or inlining them could save about 4.8 s.
Use efficient cache lifetimes
2.5 s · 444 KiB12 files are served with short cache lifetimes, so returning visitors download them again (444 KiB).
Mobile performance score: 24
24/100Your mobile performance score is 24 (desktop: 64). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 6.4 s
A phone's processor spends 6.4 s on main-thread work while loading, 2.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Clarity and website-files.com and others), adding 16.8 MB and 2.2 s of main-thread time.
website-files.com adds 494 ms
494 mswebsite-files.com costs a phone 494 ms of main-thread work and 15.6 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.
Reduce unused JavaScript
950 ms · 652 KiBAbout 652 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 950 ms faster on a phone.
17 long tasks on the main thread
17 long tasks block the main thread while loading, the longest for 1.2 s. During a long task the page ignores taps.
Reduce unused CSS
650 ms · 112 KiBAbout 112 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 650 ms faster on a phone.
Google Tag Manager adds 591 ms
591 msGoogle Tag Manager costs a phone 591 ms of main-thread work and 522 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.
Clarity adds 576 ms
576 msClarity costs a phone 576 ms of main-thread work and 27 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.
Minify CSS
300 ms · 23 KiB23 KiB could be saved by minifying CSS.
1,673 HTML elements
The page has 1,673 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Legacy JavaScript
23 KiBPolyfills for old browsers add 23 KiB JavaScript that modern phones do not need.
Phones get a much slower page than desktops
Desktop scores 64 but mobile only 24. 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.
1 checks passed
Server response: 3 ms
3 msYour server sent the HTML in 3 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 52.0 s
52.0 sYour largest element takes 52.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Your growth and product teams can launch immersive experien…”.
Time to Interactive: 61.1 s
61.1 sThe page becomes fully interactive after 61.1 s. Good is under 3.8 s.
Total Blocking Time: 2.8 s
2.8 sScripts block taps and scrolling for 2.8 s in total while the page loads. Good is under 200 ms.
First Contentful Paint: 5.0 s
5.0 sThe first text or image appears after 5.0 s on a phone. Good is under 1.8 s.
Speed Index: 8.3 s
8.3 sVisually, the page fills in at 8.3 s (Speed Index). Good is under 3.4 s.
Cumulative Layout Shift: 0.131
0.131The layout shifts by 0.131 while loading, so content jumps under the reader's thumb. Good is under 0.1.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
+2%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.6 s to 2.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Not enough real-visitor data yet
Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.
Images and page weight
Page weight: 17.3 MB in 212 requests
17.3 MBYour homepage downloads 17.3 MB in 212 requests on a phone: images 12.6 MB (94), other files 2.7 MB (60) and scripts 1.5 MB (30). Under 2 MB keeps phones on slow connections fast.
3 images over 500 KB
3 images weigh 10.0 MB together. On a phone connection a single image that size takes seconds.
3 images in older formats
3 images (10.0 MB) 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.
2 images far larger than shown
181 KiB2 images are downloaded at several times the size a phone draws them, for example 64ff458f40b240b6cbbd56d4_6311abbd34332ac61141e1b4_apxor-clie at 428 px wide, shown at 50 px. Resized copies would save about 181 KiB.
About 4.9 g of CO₂ per visit
4.91 gBy the Sustainable Web Design model, a visit to your homepage emits about 4.91 g of CO₂e: 589.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
5 text elements with low contrast
5 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 (41 elements)
All page content should be contained by landmarks: 41 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.
2 checks passed
Every image has alt text
All 247 images in the HTML carry an alt attribute.
37 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: 37 passed and 3 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
Meta description is long (175 characters)
Your meta description is 175 characters; Google truncates after about 160, so the end of your pitch is cut.
18 links with vague text
18 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
93 internal links, 12 external
The homepage links to 93 pages on apxor.com and 12 external pages.
6 checks passed
One H1 headline
Your main headline reads: “Product Engagement Made Easy”.
Title: 55 characters
Your title is a healthy 55 characters: “Apxor | World's First Digital Nudging Platform for Apps”.
Canonical URL set
The canonical URL is https://www.apxor.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.apxor.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.apxor.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 (2,285 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages without a meta description
https://www.apxor.com/ebooks and https://www.apxor.com/webinars/product-strategies-with-ankur-warikoo have no meta description, so Google writes the search snippet from whatever text it finds.
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.apxor.com/development/pricing-old, whose canonical is https://www.apxor.com/pricing. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 22 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.
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 15 pages that loaded have a <title>.
Best practices
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
16 of 16 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 629 words of copy
The homepage carries about 629 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”.
47 calls to action
The homepage has 47 calls to action, for example “Register Now”, “Pricing” and “Contact Us”.
Social proof on the page
Social proof on the homepage: 17 testimonial or review blocks, 55 customer or partner logos, 7 trust badges and “More than 41K users”.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics, Meta Pixel and Mixpanel.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
Privacy and tracking
8 trackers load before any consent
8Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Meta Pixel and 3 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.
17 cookies set on arrival
17Opening the homepage sets 17 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.
36 other companies contacted
Loading the homepage contacts 36 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 apxor.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 | Mixpanel
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 apxor.com, including 21 speed issues and 3 SEO issues. 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.