Website review, no card needed
byparra.us website review
Visit site (opens in a new tab)Reviewed 9 November 202627 issues · 75 checks
This review found 27 issues worth fixing on byparra.us, 6 of them high impact, across 75 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
84B- #19,786 of 108,953 reviewed websitesbeats 77%
- #12,886 of 61,775 online storesbeats 73%
- #12,516 of 56,370 Shopify storesbeats 71%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 988 ms |
| May 30, 2026 | 825 ms |
| Jun 6, 2026 | 785 ms |
| Jun 13, 2026 | 797 ms |
| Jun 20, 2026 | 849 ms |
| Jun 27, 2026 | 839 ms |
| Jul 4, 2026 | 788 ms |
| Jul 11, 2026 | 767 ms |
| Jul 18, 2026 | 742 ms |
| Jul 25, 2026 | 822 ms |
| Aug 1, 2026 | 936 ms |
| Aug 8, 2026 | 840 ms |
| Aug 15, 2026 | 805 ms |
| Aug 22, 2026 | 773 ms |
| Aug 29, 2026 | 748 ms |
| Sep 5, 2026 | 809 ms |
| Sep 12, 2026 | 825 ms |
| Sep 19, 2026 | 763 ms |
| Sep 26, 2026 | 692 ms |
| Oct 3, 2026 | 671 ms |
| Oct 10, 2026 | 663 ms |
| Oct 17, 2026 | 696 ms |
| Oct 24, 2026 | 741 ms |
| Oct 31, 2026 | 709 ms |
| Nov 7, 2026 | 685 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 53 ms |
| May 30, 2026 | 51 ms |
| Jun 6, 2026 | 51 ms |
| Jun 13, 2026 | 51 ms |
| Jun 20, 2026 | 53 ms |
| Jun 27, 2026 | 51 ms |
| Jul 4, 2026 | 49 ms |
| Jul 11, 2026 | 49 ms |
| Jul 18, 2026 | 48 ms |
| Jul 25, 2026 | 49 ms |
| Aug 1, 2026 | 54 ms |
| Aug 8, 2026 | 52 ms |
| Aug 15, 2026 | 49 ms |
| Aug 22, 2026 | 47 ms |
| Aug 29, 2026 | 49 ms |
| Sep 5, 2026 | 48 ms |
| Sep 12, 2026 | 50 ms |
| Sep 19, 2026 | 50 ms |
| Sep 26, 2026 | 50 ms |
| Oct 3, 2026 | 48 ms |
| Oct 10, 2026 | 48 ms |
| Oct 17, 2026 | 49 ms |
| Oct 24, 2026 | 49 ms |
| Oct 31, 2026 | 54 ms |
| Nov 7, 2026 | 54 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
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.
Mobile performance score: 72
72/100Your mobile performance score is 72. Pages that score under 90 lose visitors before the first paint.
Improve image delivery
200 ms · 136 KiB8 images could be 136 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 200 ms faster on a phone.
Use efficient cache lifetimes
150 ms · 5 KiB3 files are served with short cache lifetimes, so returning visitors download them again (5 KiB).
6 third-party services on the page
6 third-party services load with your homepage (jQuery CDN, Shopify and spicegems.org and others), adding 187 KiB and 120 ms of main-thread time.
2 long tasks on the main thread
2 long tasks block the main thread while loading, the longest for 88 ms. During a long task the page ignores taps.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
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: 0.8 s
A phone's processor spends 0.8 s on main-thread work while loading, 298 ms of it running JavaScript. That is comfortably low.
Server response: 6 ms
6 msYour server sent the HTML in 6 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.
Largest Contentful Paint: 5.5 s
5.5 sYour largest element takes 5.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Lowercase script logo beanie”.
Real-user TTFB: 808 ms
808 msReal visitors wait 808 ms for your server to start answering (75th percentile). Good is under 800 ms.
40 images without width and height
40 images have no width and height attributes, so the layout jumps as each one loads.
Speed Index: 5.0 s
5.0 sVisually, the page fills in at 5.0 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.6 s
2.6 sThe first text or image appears after 2.6 s on a phone. Good is under 1.8 s.
Time to Interactive: 5.6 s
5.6 sThe page becomes fully interactive after 5.6 s. Good is under 3.8 s.
Tap response (INP) held steady for real visitors
+4%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 53 ms to 54 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 checks passed
Real-user LCP: 0.7 s
0.7 sReal visitors wait 0.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 53 ms
53 msReal visitors wait 53 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: 0.6 s
0.6 sReal visitors see the first content after 0.6 s (75th percentile). Good is under 1.8 s.
Largest content (LCP) got 23% faster for real visitors
-23%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.0 s to 0.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 19 ms
19 msScripts block the page for only 19 ms while loading. Good is under 200 ms.
Images and page weight
About 0.4 g of CO₂ per visit
0.42 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.42 g of CO₂e: 50.9 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.5 MB in 147 requests
1.5 MBYour homepage downloads 1.5 MB in 147 requests on a phone: other files 655 KiB (62), images 390 KiB (27) and scripts 279 KiB (40). 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 image without alt text
1 image has no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (57 elements)
All page content should be contained by landmarks: 57 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.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
5 links without text
5 visible links have no text or label, so screen readers cannot say where they go.
3 form fields without a label
3 form fields have no label, so screen readers announce an empty box and autofill guesses.
1 checks passed
30 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 35 WCAG 2.2 A/AA and best-practice rules on the phone render: 30 passed and 5 failed. 1 more 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.
Title is short (22 characters)
Your title is only 22 characters: “by Parra – by Parra US”. 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.
Meta description is short (51 characters)
Your meta description is only 51 characters: “exclusive products from artist Parra from Amsterdam”. 70 to 160 characters is enough to sell the click.
65 internal links, 2 external
The homepage links to 65 pages on byparra.us and 2 external pages.
4 checks passed
Canonical URL set
The canonical URL is https://www.byparra.us/.
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.byparra.us/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.
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 (185 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.byparra.us/llms.txt (5 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
14 pages without a meta description
https://www.byparra.us/collections/all-products, https://www.byparra.us/collections/apparel, https://www.byparra.us/collections/t-shirts, https://www.byparra.us/collections/sweats, https://www.byparra.us/collections/knitwear and https://www.byparra.us/collections/pants-shorts and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.
14 pages without an H1
https://www.byparra.us/collections/all-products, https://www.byparra.us/collections/apparel, https://www.byparra.us/collections/t-shirts, https://www.byparra.us/collections/sweats, https://www.byparra.us/collections/knitwear and https://www.byparra.us/collections/pants-shorts and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.
9 pages with very little text
https://www.byparra.us/collections/knitwear, https://www.byparra.us/collections/pants-shorts, https://www.byparra.us/collections/jackets, https://www.byparra.us/collections/socks, https://www.byparra.us/collections/bags and https://www.byparra.us/collections/home-textiles and 3 others have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 61 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.
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 15 pages that loaded have a <title>.
Best practices
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
34 of 38 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
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.
Thin social proof
Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.
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.
Only about 174 words
The homepage has only about 174 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
2 checks passed
3 calls to action
The homepage has 3 calls to action, for example “Contact”, “Amsterdam Shop” and “Subscribe”.
1 short form
A short form (2 fields at most) is right on the homepage, asking for an email.
Privacy and tracking
6 cookies set on arrival
6Opening the homepage sets 6 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.
7 other companies contacted
Loading the homepage contacts 7 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 byparra.us, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Apps on your store
Your storefront loads 1 app. It is code from another company running for your shoppers.
Apps your storefront loads
Geoip Country Redirect
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 27 issues on byparra.us, including 9 speed issues, 4 SEO issues 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.