Website review, no card needed
apparell.com website review
Visit site (opens in a new tab)Reviewed 5 November 202621 issues · 96 checks
This review found 21 issues worth fixing on apparell.com, 9 of them high impact, across 96 checks. The most urgent: page weight: 62.2 MB in 209 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
88B- #3,763 of 80,918 reviewed websitesbeats 93%
- #1,843 of 39,887 online storesbeats 93%
- #1,777 of 35,280 Shopify storesbeats 92%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.4 s |
| May 23, 2026 | 1.4 s |
| May 30, 2026 | 1.4 s |
| Jun 6, 2026 | 1.4 s |
| Jun 13, 2026 | 1.4 s |
| Jun 20, 2026 | 1.4 s |
| Jun 27, 2026 | 1.4 s |
| Jul 4, 2026 | 1.4 s |
| Jul 11, 2026 | 1.4 s |
| Jul 18, 2026 | 1.4 s |
| Jul 25, 2026 | 1.4 s |
| Aug 1, 2026 | 1.3 s |
| Aug 8, 2026 | 1.3 s |
| Aug 15, 2026 | 1.3 s |
| Aug 22, 2026 | 1.3 s |
| Aug 29, 2026 | 1.4 s |
| Sep 5, 2026 | 1.4 s |
| Sep 12, 2026 | 1.4 s |
| Sep 19, 2026 | 1.4 s |
| Sep 26, 2026 | 1.3 s |
| Oct 3, 2026 | 1.3 s |
| Oct 10, 2026 | 1.3 s |
| Oct 17, 2026 | 1.2 s |
| Oct 24, 2026 | 1.2 s |
| Oct 31, 2026 | 1.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 104 ms |
| May 23, 2026 | 109 ms |
| May 30, 2026 | 113 ms |
| Jun 6, 2026 | 115 ms |
| Jun 13, 2026 | 113 ms |
| Jun 20, 2026 | 111 ms |
| Jun 27, 2026 | 108 ms |
| Jul 4, 2026 | 105 ms |
| Jul 11, 2026 | 107 ms |
| Jul 18, 2026 | 110 ms |
| Jul 25, 2026 | 111 ms |
| Aug 1, 2026 | 111 ms |
| Aug 8, 2026 | 112 ms |
| Aug 15, 2026 | 110 ms |
| Aug 22, 2026 | 108 ms |
| Aug 29, 2026 | 106 ms |
| Sep 5, 2026 | 105 ms |
| Sep 12, 2026 | 110 ms |
| Sep 19, 2026 | 113 ms |
| Sep 26, 2026 | 114 ms |
| Oct 3, 2026 | 115 ms |
| Oct 10, 2026 | 111 ms |
| Oct 17, 2026 | 111 ms |
| Oct 24, 2026 | 112 ms |
| Oct 31, 2026 | 111 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.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
apparell.com does not allow embedding, so this is Google's rendering of the page.
Speed
Render-blocking requests
1.1 s18 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.
Improve image delivery
217 KiB8 images could be 217 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
4 third-party services on the page
4 third-party services load with your homepage (Shopify, 506.io and Unpkg and others), adding 342 KiB and 157 ms of main-thread time.
Reduce unused JavaScript
111 KiBAbout 111 KiB of JavaScript is downloaded but never used on this page.
1 long task on the main thread
1 long task block the main thread while loading, the longest for 65 ms. During a long task the page ignores taps.
Reduce unused CSS
20 ms · 39 KiBAbout 39 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 20 ms faster on a phone.
Legacy JavaScript
22 KiBPolyfills for old browsers add 22 KiB JavaScript that modern phones do not need.
Use efficient cache lifetimes
15 KiB4 files are served with short cache lifetimes, so returning visitors download them again (15 KiB).
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.
Minify CSS
3 KiB3 KiB could be saved by minifying CSS.
Duplicated JavaScript
2 KiB2 KiB JavaScript is shipped twice across bundles.
3 checks passed
Mobile performance score: 99
99/100Your mobile performance score is 99. That is in Google's “good” band (90 and up).
Main-thread work: 1.5 s
A phone's processor spends 1.5 s on main-thread work while loading, 461 ms of it running JavaScript. That is comfortably low.
Server response: 39 ms
39 msYour server sent the HTML in 39 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 5.4 s
5.4 sThe page becomes fully interactive after 5.4 s. Good is under 3.8 s.
Tap response (INP) held steady for real visitors
+5%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 104 ms to 111 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
12 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 1.1 s
1.1 sReal visitors wait 1.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 115 ms
115 msReal visitors wait 115 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.1 s
1.1 sReal visitors see the first content after 1.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 533 ms
533 msReal visitors wait 533 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 14% faster for real visitors
-14%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.4 s to 1.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 1.5 s
1.5 sThe first text or image appears after 1.5 s, inside the 1.8 s “good” threshold.
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.
Cumulative Layout Shift: 0.001
0.001The layout barely moves while loading (CLS 0.001, good is under 0.1).
Largest Contentful Paint: 1.5 s
1.5 sYour largest element renders in 1.5 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “It’s not a product. It’s Culture.”.
Total Blocking Time: 15 ms
15 msScripts block the page for only 15 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 62.2 MB in 209 requests
62.2 MBYour homepage downloads 62.2 MB in 209 requests on a phone: media 60.1 MB (14), other files 742 KiB (85) and images 599 KiB (26). Under 2 MB keeps phones on slow connections fast.
About 17.6 g of CO₂ per visit
17.62 gBy the Sustainable Web Design model, a visit to your homepage emits about 17.62 g of CO₂e: 2114.4 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 text elements with low contrast
2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Scrollable region must have keyboard access (1 element)
Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
1 checks passed
45 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 3 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Meta description is long (173 characters)
Your meta description is 173 characters; Google truncates after about 160, so the end of your pitch is cut.
40 internal links, 2 external
The homepage links to 40 pages on apparell.com and 2 external pages.
7 checks passed
One H1 headline
Your main headline reads: “Apparell™ | It's not a product, it's Culture”.
Title: 44 characters
Your title is a healthy 44 characters: “Apparell™ | It's not a product, it's Culture”.
Canonical URL set
The canonical URL is https://apparell.com/.
Structured data in place
Structured data found: BreadcrumbList, Organization and WebSite.
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://apparell.com/sitemap.xml.
AI search readiness
Organization data is thin (2 of 6 facts)
Your Organization JSON-LD is missing logo, sameAs (social profiles), 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.
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.
Text is in the HTML
Your server sends the page's text in the HTML (721 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes /llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
2 pages share a title
/collections/boutique/products/camiseta-azul-aldhara and /collections/boutique/products/camiseta-negra-aldhara all use the title “Calblanque - Camiseta Blanca Calblanque | Apparell™”. Search engines can't tell which page to show for a search, so each competes with the others.
1 page without a meta description
/policies/shipping-policy has no meta description, so Google writes the search snippet from whatever text it finds.
5 links to non-canonical URLs
Your homepage links to 5 pages by a URL that isn't their canonical one, for example /collections/boutique/products/cortavientos-lacosta, whose canonical is /products/cortavientos-lacosta. 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 25 found) and read each the way a search engine does.
4 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
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
1 broken image
1 image failed to load on a phone, for example https://apparell.com/.
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
14 of 15 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Security and trust
Short HSTS lifetime
HSTS is set, but max-age is 91 days; one year is the recommended minimum.
No Referrer-Policy
No Referrer-Policy header, so full URLs can leak to the sites you link to.
No Permissions-Policy
No Permissions-Policy header to switch off camera, microphone and location for embedded content.
Deprecated X-XSS-Protection
X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.
No security.txt
There is no /.well-known/security.txt telling researchers how to report a security problem to you.
7 checks passed
Served over HTTPS
The homepage is served over HTTPS (apparell.com).
Valid certificate (59 days left)
The certificate from Let's Encrypt · YE2 verifies for apparell.com and is valid for another 59 days.
Protected from clickjacking
X-Frame-Options or a frame-ancestors policy stops other sites framing yours.
Content-Security-Policy set
A Content-Security-Policy is set, the main browser-side defence against injected scripts.
http:// redirects to https
http://apparell.com redirects to the secure version.
HTTP/2 and HTTP/3
The server speaks HTTP/2 and advertises HTTP/3, so browsers load many files over one connection.
All 35 links work
All 35 links checked from your homepage (34 internal, 1 external) answered without errors.
Domain and trust
No CAA record
apparell.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.
DNSSEC is off
apparell.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.
2 checks passed
Domain is 13 years old
13 yearsapparell.com was registered in May 2013 through Soluciones Corporativas IP, SL. An established domain carries more trust with email providers and search engines.
Registered until May 2034
apparell.com is registered until May 2034.
Content and conversion
No call to action on the first screen
On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.
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 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 345 words of copy
The homepage carries about 345 words of visible text.
1 checks passed
11 short forms
11 short forms (2 fields at most) are right on the homepage, asking for an email.
Email authentication
DMARC is monitor-only (p=none)
DMARC is set to p=none, so mail pretending to be apparell.com is still delivered. Add a report address, check the reports, then move to quarantine.
Email authentication score: 70/100
Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.
2 checks passed
SPF in place (~all)
An SPF record lists your sending servers and marks other mail as suspicious (~all): “v=spf1 include:_spf.google.com include:mail.zendesk.com include:amazonses.com ~all”.
DKIM signing found
A DKIM key is published (selector “google” and “mail”), so receivers can verify mail really came from you.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and TikTok 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.
14 cookies set on arrival
14Opening the homepage sets 14 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.
17 other companies contacted
Loading the homepage contacts 17 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
Apps on your store
Your storefront loads 5 apps. Each one is code from another company running for your shoppers.
None of the apps your storefront loads is on the list of apps with a known security problem.
Apps your storefront loads
Apparell Custom App · Seowill Ai Seo · Eg Auto Add To Cart · Frontend · Simple Bundle
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
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 21 issues on apparell.com, including 2 speed issues, 1 SEO issue and 5 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.