Website review, no card needed
bywoops.com website review
Visit site (opens in a new tab)Reviewed 22 October 202628 issues · 74 checks
This review found 28 issues worth fixing on bywoops.com, 8 of them high impact, across 74 checks. The most urgent: improve image delivery. 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
84BClosest competitors among Wix websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 971 ms |
| May 9, 2026 | 1.1 s |
| May 16, 2026 | 1.1 s |
| May 23, 2026 | 1.1 s |
| May 30, 2026 | 1.1 s |
| Jun 6, 2026 | 1.1 s |
| Jun 13, 2026 | 1.0 s |
| Jun 20, 2026 | 1.1 s |
| Jun 27, 2026 | 1.2 s |
| Jul 4, 2026 | 1.1 s |
| Jul 11, 2026 | 1.1 s |
| Jul 18, 2026 | 1.1 s |
| Jul 25, 2026 | 1.0 s |
| Aug 1, 2026 | 1.2 s |
| Aug 8, 2026 | 1.1 s |
| Aug 15, 2026 | 1.1 s |
| Aug 22, 2026 | 1.1 s |
| Aug 29, 2026 | 1.3 s |
| Sep 5, 2026 | 1.5 s |
| Sep 12, 2026 | 1.5 s |
| Sep 19, 2026 | 1.5 s |
| Sep 26, 2026 | 1.4 s |
| Oct 3, 2026 | 1.4 s |
| Oct 10, 2026 | 1.3 s |
| Oct 17, 2026 | 1.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 112 ms |
| May 9, 2026 | 119 ms |
| May 16, 2026 | 125 ms |
| May 23, 2026 | 124 ms |
| May 30, 2026 | 125 ms |
| Jun 6, 2026 | 127 ms |
| Jun 13, 2026 | 112 ms |
| Jun 20, 2026 | 116 ms |
| Jun 27, 2026 | 118 ms |
| Jul 4, 2026 | 115 ms |
| Jul 11, 2026 | 120 ms |
| Jul 18, 2026 | 134 ms |
| Jul 25, 2026 | 122 ms |
| Aug 1, 2026 | 128 ms |
| Aug 8, 2026 | 121 ms |
| Aug 15, 2026 | 125 ms |
| Aug 22, 2026 | 125 ms |
| Aug 29, 2026 | 145 ms |
| Sep 5, 2026 | 150 ms |
| Sep 12, 2026 | 129 ms |
| Sep 19, 2026 | 121 ms |
| Sep 26, 2026 | 97 ms |
| Oct 3, 2026 | 77 ms |
| Oct 10, 2026 | 70 ms |
| Oct 17, 2026 | 63 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
Speed
Improve image delivery
3.6 s · 708 KiB2 images could be 708 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.6 s faster on a phone.
Wix adds 1.2 s
1.2 sWix costs a phone 1.2 s of main-thread work and 1.2 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.
Use efficient cache lifetimes
450 ms · 4.5 MB32 files are served with short cache lifetimes, so returning visitors download them again (4.5 MB).
6 third-party services on the page
6 third-party services load with your homepage (Wix, Accessibe Accessibility Overlay and Google Tag Manager and others), adding 14.2 MB and 1.5 s of main-thread time.
Instagram adds 0 ms
0 msInstagram costs a phone 0 ms of main-thread work and 12.5 MB 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.
Mobile performance score: 60
60/100Your mobile performance score is 60 (desktop: 73). Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
310 ms · 435 KiBAbout 435 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 310 ms faster on a phone.
Main-thread work: 3.5 s
A phone's processor spends 3.5 s on main-thread work while loading, 2.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
9 long tasks on the main thread
9 long tasks block the main thread while loading, the longest for 201 ms. During a long task the page ignores taps.
Duplicated JavaScript
150 ms · 31 KiB31 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 150 ms faster on a phone.
Reduce unused CSS
57 KiBAbout 57 KiB of CSS is downloaded but never applied on this page.
Legacy JavaScript
12 KiBPolyfills for old browsers add 12 KiB JavaScript that modern phones do not need.
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.
1 checks passed
Server response: 38 ms
38 msYour server sent the HTML in 38 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 9.8 s
9.8 sYour largest element takes 9.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Homepage Banner Mobile.jpg”.
Time to Interactive: 18.1 s
18.1 sThe page becomes fully interactive after 18.1 s. Good is under 3.8 s.
First Contentful Paint: 3.2 s
3.2 sThe first text or image appears after 3.2 s on a phone. Good is under 1.8 s.
Speed Index: 4.3 s
4.3 sVisually, the page fills in at 4.3 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 303 ms
303 msScripts block taps and scrolling for 303 ms in total while the page loads. Good is under 200 ms.
Largest content (LCP) got 18% slower for real visitors
+18%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 1.0 s to 1.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 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.4 s
1.4 sReal visitors wait 1.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
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.8 s
0.8 sReal visitors see the first content after 0.8 s (75th percentile). Good is under 1.8 s.
Tap response (INP) got 42% faster for real visitors
-42%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 112 ms to 63 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.021
0.021The layout barely moves while loading (CLS 0.021, good is under 0.1).
Images and page weight
Page weight: 15.2 MB in 243 requests
15.2 MBYour homepage downloads 15.2 MB in 243 requests on a phone: images 9.0 MB (36), media 3.6 MB (2) and scripts 1.5 MB (107). Under 2 MB keeps phones on slow connections fast.
About 4.3 g of CO₂ per visit
4.30 gBy the Sustainable Web Design model, a visit to your homepage emits about 4.30 g of CO₂e: 515.9 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
24 text elements with low contrast
24 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
2 checks passed
Every image has alt text
All 10 images in the HTML carry an alt attribute.
44 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 46 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 2 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
2 H1 headlines
There are 2 <h1> headlines (“ORDER FROM NEAREST STORE” and “ORDER FROM NEAREST STORE”). One clear main headline is easier for people and search engines.
Meta description is long (170 characters)
Your meta description is 170 characters; Google truncates after about 160, so the end of your pitch is cut.
17 internal links, 11 external
The homepage links to 17 pages on bywoops.com and 11 external pages.
6 checks passed
Title: 49 characters
Your title is a healthy 49 characters: “French Macarons Near Me | Woops! Macarons & Gifts”.
Canonical URL set
The canonical URL is https://www.bywoops.com/.
Structured data in place
Structured data found: 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://www.bywoops.com/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.
2 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.
llms.txt published
The site publishes https://www.bywoops.com/llms.txt (3 KiB, 3 links), a plain-text guide to the site for AI tools.
Other pages
1 linked page hidden from search
https://www.bywoops.com/shop-local is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
7 pages without an H1
https://www.bywoops.com/shop-local, https://www.bywoops.com/locations-list, https://www.bywoops.com/flavor-guide, https://www.bywoops.com/corporate-gifting, https://www.bywoops.com/faq and https://www.bywoops.com/return-and-refund-policy and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.
7 internal pages checked
We fetched 7 pages linked from your homepage and read each the way a search engine does.
5 checks passed
Linked pages load
All 7 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 7 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
Every page has a title
All 7 pages that loaded have a <title>.
Best practices
15 small tap targets
15 of 22 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 “globalThis.defineStrictProperty is not a function”.
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.
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
Only about 129 words
The homepage has only about 129 words of visible text; thin pages give Google and first-time buyers little to go on.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP NOW”.
4 calls to action
The homepage has 4 calls to action, for example “Pop Shop”, “SHOP NOW” and “Subscribe”.
1 short form
A short form (2 fields at most) is right on the homepage, asking for an email.
Direct contact links
Visitors can reach you directly: 1 phone link and 1 email link.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads Google Tag Manager (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.
7 cookies set on arrival
7Opening the homepage sets 7 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.
10 other companies contacted
Loading the homepage contacts 10 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 bywoops.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- Wix
- Framework
- React
Company
- Founded
- 2012
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 28 issues on bywoops.com, including 13 speed issues, 2 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.