Website review, no card needed
wixsite.com website review
Visit site (opens in a new tab)Reviewed 6 November 202632 issues · 68 checks
This review found 32 issues worth fixing on wixsite.com, 13 of them high impact, across 68 checks. The most urgent: google Tag Manager adds 1.4 s. 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
78CClosest competitors among Wix websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.8 s |
| May 23, 2026 | 2.8 s |
| May 30, 2026 | 2.8 s |
| Jun 6, 2026 | 2.8 s |
| Jun 13, 2026 | 2.9 s |
| Jun 20, 2026 | 3.0 s |
| Jun 27, 2026 | 3.0 s |
| Jul 4, 2026 | 3.1 s |
| Jul 11, 2026 | 3.1 s |
| Jul 18, 2026 | 3.1 s |
| Jul 25, 2026 | 3.1 s |
| Aug 1, 2026 | 3.0 s |
| Aug 8, 2026 | 3.0 s |
| Aug 15, 2026 | 3.0 s |
| Aug 22, 2026 | 3.1 s |
| Aug 29, 2026 | 3.1 s |
| Sep 5, 2026 | 3.1 s |
| Sep 12, 2026 | 3.1 s |
| Sep 19, 2026 | 3.0 s |
| Sep 26, 2026 | 3.0 s |
| Oct 3, 2026 | 3.0 s |
| Oct 10, 2026 | 3.0 s |
| Oct 17, 2026 | 2.9 s |
| Oct 24, 2026 | 2.9 s |
| Oct 31, 2026 | 2.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 209 ms |
| May 23, 2026 | 207 ms |
| May 30, 2026 | 207 ms |
| Jun 6, 2026 | 209 ms |
| Jun 13, 2026 | 212 ms |
| Jun 20, 2026 | 215 ms |
| Jun 27, 2026 | 221 ms |
| Jul 4, 2026 | 227 ms |
| Jul 11, 2026 | 227 ms |
| Jul 18, 2026 | 229 ms |
| Jul 25, 2026 | 230 ms |
| Aug 1, 2026 | 229 ms |
| Aug 8, 2026 | 235 ms |
| Aug 15, 2026 | 244 ms |
| Aug 22, 2026 | 254 ms |
| Aug 29, 2026 | 264 ms |
| Sep 5, 2026 | 271 ms |
| Sep 12, 2026 | 272 ms |
| Sep 19, 2026 | 275 ms |
| Sep 26, 2026 | 277 ms |
| Oct 3, 2026 | 283 ms |
| Oct 10, 2026 | 289 ms |
| Oct 17, 2026 | 295 ms |
| Oct 24, 2026 | 304 ms |
| Oct 31, 2026 | 311 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
Google Tag Manager adds 1.4 s
1.4 sGoogle Tag Manager costs a phone 1.4 s of main-thread work and 1.3 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Main-thread work: 7.4 s
A phone's processor spends 7.4 s on main-thread work while loading, 3.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
4,574 HTML elements
The page has 4,574 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 (Google Tag Manager, Facebook and Other Google APIs/SDKs and others), adding 1.8 MB and 1.9 s of main-thread time.
Mobile performance score: 70
70/100Your mobile performance score is 70. Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
847 KiBAbout 847 KiB of JavaScript is downloaded but never used on this page.
Facebook adds 414 ms
414 msFacebook costs a phone 414 ms of main-thread work and 312 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
321 KiB17 files are served with short cache lifetimes, so returning visitors download them again (321 KiB).
17 long tasks on the main thread
17 long tasks block the main thread while loading, the longest for 286 ms. During a long task the page ignores taps.
Legacy JavaScript
39 KiBPolyfills for old browsers add 39 KiB JavaScript that modern phones do not need.
Duplicated JavaScript
30 KiB30 KiB JavaScript is shipped twice across bundles.
Reduce unused CSS
28 KiBAbout 28 KiB of CSS is downloaded but never applied on this page.
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.
Improve image delivery
5 KiB1 image could be 5 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
1 checks passed
Server response: 28 ms
28 msYour server sent the HTML in 28 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 INP: 510 ms
510 msReal visitors wait 510 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Time to Interactive: 26.8 s
26.8 sThe page becomes fully interactive after 26.8 s. Good is under 3.8 s.
Total Blocking Time: 1.4 s
1.4 sScripts block taps and scrolling for 1.4 s in total while the page loads. Good is under 200 ms.
Tap response (INP) got 48% slower for real visitors
+48%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 209 ms to 311 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 2.2 s
2.2 sReal visitors see the first content after 2.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 874 ms
874 msReal visitors wait 874 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 2.3 s
2.3 sThe first text or image appears after 2.3 s on a phone. Good is under 1.8 s.
Largest content (LCP) held steady for real visitors
+4%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.8 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.4 s
2.4 sReal visitors wait 2.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.02
0.02For real visitors the layout shifts by 0.02 (75th percentile). Good is under 0.1.
Largest Contentful Paint: 2.3 s
2.3 sYour largest element renders in 2.3 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Create your future on the leading website builder”.
Speed Index: 2.8 s
2.8 sVisually, the page fills in at 2.8 s (Speed Index), inside the 3.4 s “good” threshold.
Cumulative Layout Shift: 0.023
0.023The layout barely moves while loading (CLS 0.023, good is under 0.1).
Images and page weight
Page weight: 4.9 MB in 376 requests
4.9 MBYour homepage downloads 4.9 MB in 376 requests on a phone: scripts 2.8 MB (127), other files 1.5 MB (178) and HTML 299 KiB (3). Under 2 MB keeps phones on slow connections fast.
About 1.4 g of CO₂ per visit
1.38 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.38 g of CO₂e: 165.7 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 tap targets too small
2 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.
Elements marked as presentational should be consistently ignored (1 element)
Elements marked as presentational should be consistently ignored: 1 element on the page fails this check, rated minor by axe-core.
1 checks passed
54 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 56 WCAG 2.2 A/AA and best-practice rules on the phone render: 54 passed and 2 failed. 4 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.
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.
7 checks passed
Meta description: 144 characters
Your meta description is 144 characters: “Build the business you have in mind on a platform trusted by millions. Hosting, business tools, domains and marketing b…”.
Title: 56 characters
Your title is a healthy 56 characters: “Wix.com - The platform trusted by millions of businesses”.
Canonical URL set
The canonical URL is https://www.wix.com/.
Structured data in place
Structured data found: FAQPage, HowTo, Organization and VideoObject.
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.wix.com/sitemap.xml.
AI search readiness
Most text only appears after JavaScript runs
0%A phone browser shows 1,437 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.
3 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.
Organization data: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.
llms.txt published
The site publishes https://www.wix.com/llms.txt (37 KiB, 235 links), a plain-text guide to the site for AI tools.
Best practices
3 small tap targets
3 of 12 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “globalThis.defineStrictProperty is not a function”.
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 analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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,437 words of copy
The homepage carries about 1,437 words of visible text.
1 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Start for free” and “Get Started”.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Microsoft Ads and 1 more (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.
18 cookies set on arrival
18Opening the homepage sets 18 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.
28 other companies contacted
Loading the homepage contacts 28 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 wixsite.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Hosting
- Wix
Company
- Headquarters
- Dublin
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 wixsite.com, including 17 speed issues, 3 SEO issues and 4 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.