Website review, no card needed
techxr.co website review
Visit site (opens in a new tab)Reviewed 21 October 202642 issues · 71 checks
This review found 42 issues worth fixing on techxr.co, 18 of them high impact, across 71 checks. The most urgent: use efficient cache lifetimes. 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
58F- #109,192 of 111,105 reviewed websitesbeats 1%
- #63,035 of 63,365 online storesbeats 0%
- #57,631 of 57,856 Shopify storesbeats 0%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 4.3 s |
| May 9, 2026 | 4.4 s |
| May 16, 2026 | 4.4 s |
| May 23, 2026 | 4.4 s |
| May 30, 2026 | 4.4 s |
| Jun 6, 2026 | 4.4 s |
| Jun 13, 2026 | 4.5 s |
| Jun 20, 2026 | 4.5 s |
| Jun 27, 2026 | 4.6 s |
| Jul 4, 2026 | 4.6 s |
| Jul 11, 2026 | 4.6 s |
| Jul 18, 2026 | 4.6 s |
| Jul 25, 2026 | 4.4 s |
| Aug 1, 2026 | 4.5 s |
| Aug 8, 2026 | 4.6 s |
| Aug 15, 2026 | 4.6 s |
| Aug 22, 2026 | 4.6 s |
| Aug 29, 2026 | 4.5 s |
| Sep 5, 2026 | 4.4 s |
| Sep 12, 2026 | 4.3 s |
| Sep 19, 2026 | 4.4 s |
| Sep 26, 2026 | 4.4 s |
| Oct 3, 2026 | 4.5 s |
| Oct 10, 2026 | 4.5 s |
| Oct 17, 2026 | 4.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 260 ms |
| May 9, 2026 | 253 ms |
| May 16, 2026 | 241 ms |
| May 23, 2026 | 234 ms |
| May 30, 2026 | 252 ms |
| Jun 6, 2026 | 238 ms |
| Jun 13, 2026 | 235 ms |
| Jun 20, 2026 | 220 ms |
| Jun 27, 2026 | 214 ms |
| Jul 4, 2026 | 216 ms |
| Jul 11, 2026 | 224 ms |
| Jul 18, 2026 | 218 ms |
| Jul 25, 2026 | 224 ms |
| Aug 1, 2026 | 235 ms |
| Aug 8, 2026 | 243 ms |
| Aug 15, 2026 | 251 ms |
| Aug 22, 2026 | 251 ms |
| Aug 29, 2026 | 243 ms |
| Sep 5, 2026 | 228 ms |
| Sep 12, 2026 | 228 ms |
| Sep 19, 2026 | 232 ms |
| Sep 26, 2026 | 239 ms |
| Oct 3, 2026 | 259 ms |
| Oct 10, 2026 | 263 ms |
| Oct 17, 2026 | 270 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
Use efficient cache lifetimes
5.5 s · 36.3 MB110 files are served with short cache lifetimes, so returning visitors download them again (36.3 MB).
Improve image delivery
2.5 s · 26.8 MB59 images could be 26.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.5 s faster on a phone.
Reduce unused JavaScript
3.1 s · 578 KiBAbout 578 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.1 s faster on a phone.
Render-blocking requests
2.4 s8 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.4 s.
Mobile performance score: 53
53/100Your mobile performance score is 53 (desktop: 64). Pages that score under 90 lose visitors before the first paint.
Reduce unused CSS
300 ms · 37 KiBAbout 37 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.
Google Tag Manager adds 176 ms
176 msGoogle Tag Manager costs a phone 176 ms of main-thread work and 446 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.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Facebook and jQuery CDN and others), adding 869 KiB and 325 ms of main-thread time.
Legacy JavaScript
200 ms · 23 KiBPolyfills for old browsers add 23 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.
6 long tasks on the main thread
6 long tasks block the main thread while loading, the longest for 94 ms. During a long task the page ignores taps.
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.2 s
A phone's processor spends 1.2 s on main-thread work while loading, 555 ms of it running JavaScript. That is comfortably low.
Server response: 1 ms
1 msYour server sent the HTML in 1 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: 5.0 s
5.0 sReal visitors wait 5.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.47
0.47For real visitors the layout shifts by 0.47 (75th percentile). Good is under 0.1.
Largest Contentful Paint: 15.5 s
15.5 sYour largest element takes 15.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
First Contentful Paint: 6.9 s
6.9 sThe first text or image appears after 6.9 s on a phone. Good is under 1.8 s.
Time to Interactive: 15.7 s
15.7 sThe page becomes fully interactive after 15.7 s. Good is under 3.8 s.
Speed Index: 7.6 s
7.6 sVisually, the page fills in at 7.6 s (Speed Index). Good is under 3.4 s.
Real-user INP: 262 ms
262 msReal visitors wait 262 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 3.0 s
3.0 sReal visitors see the first content after 3.0 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.4 s
1.4 sReal visitors wait 1.4 s for your server to start answering (75th percentile). Good is under 800 ms.
29 images without width and height
29 images have no width and height attributes, so the layout jumps as each one loads.
Cumulative Layout Shift: 0.116
0.116The layout shifts by 0.116 while loading, so content jumps under the reader's thumb. Good is under 0.1.
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 260 ms to 270 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+6%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 4.3 s to 4.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
1 checks passed
Total Blocking Time: 128 ms
128 msScripts block the page for only 128 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 46.7 MB in 135 requests
46.7 MBYour homepage downloads 46.7 MB in 135 requests on a phone: images 45.4 MB (106), scripts 1.1 MB (10) and fonts 76 KiB (7). Under 2 MB keeps phones on slow connections fast.
22 images over 500 KB
22 images weigh 37.8 MB together. On a phone connection a single image that size takes seconds.
9 images far larger than shown
5.3 MB9 images are downloaded at several times the size a phone draws them, for example vrtherpay.5bd4e9572fc316d56487.png at 2,187 px wide, shown at 290 px. Resized copies would save about 5.3 MB.
40 images in older formats
40 images (42.2 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.
19 images below the first screen load straight away
19 images further down the page (13.1 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 13.2 g of CO₂ per visit
13.23 gBy the Sustainable Web Design model, a visit to your homepage emits about 13.23 g of CO₂e: 1587.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
14 buttons without a name
14 buttons have no accessible name, so screen readers announce just “button”.
37 text elements with low contrast
37 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
15 tap targets too small
15 tap targets are too small or too close together to hit reliably with a finger.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
No page language
The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
1 checks passed
Every image has alt text
All 1 image in the HTML carry an alt attribute.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is short (6 characters)
Your title is only 6 characters: “TechXR”. Between 30 and 65 characters leaves room to say what you do and for whom.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
Meta description is long (238 characters)
Your meta description is 238 characters; Google truncates after about 160, so the end of your pitch is cut.
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.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
3 checks passed
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.
XML sitemap found
Your XML sitemap is reachable at https://techxr.co/sitemap.xml.
AI search readiness
Most text only appears after JavaScript runs
0%A phone browser shows 1,388 words, but the HTML your server sends has only 2. 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.
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://techxr.co/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.
1 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.
Best practices
6 small tap targets
6 of 28 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 “Failed to load resource: net::ERR_FAILED”.
1 checks passed
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.
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 1,388 words of copy
The homepage carries about 1,388 words of visible text.
3 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Buy Now” and “Contact Us”.
1 call to action
The homepage has 1 call to action, for example “Buy now”.
Analytics in place
Analytics detected: Google Tag Manager, Meta Pixel and Cloudflare Web Analytics.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Meta Pixel (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.
16 other companies contacted
Loading the homepage contacts 16 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 techxr.co, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- jQuery
- E-commerce
- Shopify
- Analytics
- Google Tag Manager
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 42 issues on techxr.co, including 19 speed issues, 6 SEO issues and 2 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.