Website review, no card needed
ecomparallax.com website review
Visit site (opens in a new tab)Reviewed 11 November 202618 issues · 64 checks
This review found 18 issues worth fixing on ecomparallax.com, 4 of them high impact, across 64 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
85B- #14,875 of 108,735 reviewed websitesbeats 82%
- #9,489 of 61,693 online storesbeats 79%
- #9,233 of 56,295 Shopify storesbeats 78%
Closest competitors among Shopify stores
Compare side by sideOne score from every part of this review. How it works
How it loaded on a phone
0.5 s
1.0 s
1.4 s
1.9 s
2.4 s
2.9 s
3.4 s
3.8 s
Speed
Render-blocking requests
1.1 s17 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.
Improve image delivery
150 ms · 25 KiB2 images could be 25 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.
Reduce unused CSS
150 ms · 15 KiBAbout 15 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
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 third-party service on the page
1 third-party service load with your homepage (Shopify), adding 10 KiB and 3 ms of main-thread time.
3 checks passed
Mobile performance score: 90
90/100Your mobile performance score is 90. That is in Google's “good” band (90 and up).
Main-thread work: 1.3 s
A phone's processor spends 1.3 s on main-thread work while loading, 405 ms of it running JavaScript. That is comfortably low.
Server response: 5 ms
5 msYour server sent the HTML in 5 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 3.0 s
3.0 sYour largest element takes 3.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Cumulative Layout Shift: 0.117
0.117The layout shifts by 0.117 while loading, so content jumps under the reader's thumb. Good is under 0.1.
2 images without width and height
2 images have no width and height attributes, so the layout jumps as each one loads.
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.
4 checks passed
Time to Interactive: 3.0 s
3.0 sThe page is fully interactive after 3.0 s.
Speed Index: 2.6 s
2.6 sVisually, the page fills in at 2.6 s (Speed Index), inside the 3.4 s “good” threshold.
First Contentful Paint: 1.2 s
1.2 sThe first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.
Total Blocking Time: 0 ms
0 msScripts block the page for only 0 ms while loading. Good is under 200 ms.
Images and page weight
About 0.4 g of CO₂ per visit
0.36 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.36 g of CO₂e: 42.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
4 checks passed
Page weight: 1.3 MB in 143 requests
1.3 MBYour homepage downloads 1.3 MB in 143 requests on a phone: other files 628 KiB (58), scripts 269 KiB (37) and images 152 KiB (9). That is a lean page.
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
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
12 text elements with low contrast
12 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
1 checks passed
47 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 4 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (13 characters)
Your title is only 13 characters: “Ecom Parallax”. Between 30 and 65 characters leaves room to say what you do and for whom.
Meta description is short (39 characters)
Your meta description is only 39 characters: “Creative Solution To Digital Challenges”. 70 to 160 characters is enough to sell the click.
Structured data has 1 problem
Structured data found (Organization and WebSite) but with 1 problem, for example “Organization: logo is not an absolute URL ("https:files/Artboard_1.png")”.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
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.
One H1 headline
Your <h1> is empty.
26 internal links, 5 external
The homepage links to 26 pages on ecomparallax.com and 5 external pages.
3 checks passed
Canonical URL set
The canonical URL is https://ecomparallax.com/.
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://ecomparallax.com/sitemap.xml.
AI search readiness
4 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: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (1,468 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://ecomparallax.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
5 pages without a meta description
https://ecomparallax.com/pages/our-services, https://ecomparallax.com/pages/portfolio, https://ecomparallax.com/pages/pricing, https://ecomparallax.com/pages/contact-us and https://ecomparallax.com/collections/all have no meta description, so Google writes the search snippet from whatever text it finds.
4 pages without an H1
https://ecomparallax.com/pages/about-us, https://ecomparallax.com/pages/our-services, https://ecomparallax.com/pages/portfolio and https://ecomparallax.com/pages/pricing have no <h1> headline, so visitors and search engines get no clear main topic.
6 internal pages checked
We fetched 6 pages linked from your homepage and read each the way a search engine does.
5 checks passed
Linked pages load
All 6 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 6 pages that loaded have a <title>.
Best practices
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
2 checks passed
Tap targets are thumb-sized
7 of 8 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
Phone number is not tap-to-call
Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.
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,233 words of copy
The homepage carries about 1,233 words of visible text.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Contact Us”.
12 calls to action
The homepage has 12 calls to action, for example “Pricing”, “Contact Us” and “Get Started”.
3 short forms
3 short forms (4 fields at most) are right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 110 testimonial or review blocks, 80 customer or partner logos, 1 trust badge and “500+ Businesses”.
Privacy and tracking
5 cookies set on arrival
5Opening the homepage sets 5 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.
2 other companies contacted
Loading the homepage contacts 2 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 ecomparallax.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Apps on your store
No apps were seen in the code your storefront loads.
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
- Framework
- jQuery
- E-commerce
- Shopify
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 18 issues on ecomparallax.com, including 4 speed issues, 6 SEO issues and 1 conversion gap. 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.