Website review, no card needed
lfakids.com website review
Visit site (opens in a new tab)Reviewed 20 November 202633 issues · 69 checks
This review found 33 issues worth fixing on lfakids.com, 9 of them high impact, across 69 checks. The most urgent: reduce unused JavaScript. 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
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
Reduce unused JavaScript
2.6 s · 531 KiBAbout 531 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.6 s faster on a phone.
Render-blocking requests
1.9 s8 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.9 s.
Improve image delivery
900 ms · 245 KiB2 images could be 245 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 900 ms faster on a phone.
Mobile performance score: 66
66/100Your mobile performance score is 66. Pages that score under 90 lose visitors before the first paint.
5 third-party services on the page
5 third-party services load with your homepage (Squarespace, Facebook and sqspcdn.com and others), adding 1.7 MB and 700 ms of main-thread time.
Reduce unused CSS
600 ms · 195 KiBAbout 195 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 600 ms faster on a phone.
Squarespace adds 527 ms
527 msSquarespace costs a phone 527 ms of main-thread work and 1.1 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.
Use efficient cache lifetimes
300 ms · 198 KiB5 files are served with short cache lifetimes, so returning visitors download them again (198 KiB).
squarespace-cdn.com adds 0 ms
0 mssquarespace-cdn.com costs a phone 0 ms of main-thread work and 350 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.
Legacy JavaScript
150 ms · 105 KiBPolyfills for old browsers add 105 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
5 long tasks on the main thread
5 long tasks block the main thread while loading, the longest for 200 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: 1.3 s
A phone's processor spends 1.3 s on main-thread work while loading, 623 ms of it running JavaScript. That is comfortably low.
Server response: 41 ms
41 msYour server sent the HTML in 41 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 11.3 s
11.3 sYour largest element takes 11.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Shop smarter. sell bigger. Be savvy.”.
Time to Interactive: 11.9 s
11.9 sThe page becomes fully interactive after 11.9 s. Good is under 3.8 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.
Speed Index: 3.6 s
3.6 sVisually, the page fills in at 3.6 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 223 ms
223 msScripts block taps and scrolling for 223 ms in total while the page loads. Good is under 200 ms.
1 image without width and height
1 image 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.
1 checks passed
Cumulative Layout Shift: 0.015
0.015The layout barely moves while loading (CLS 0.015, good is under 0.1).
Images and page weight
About 0.5 g of CO₂ per visit
0.54 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.54 g of CO₂e: 64.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.9 MB in 64 requests
1.9 MBYour homepage downloads 1.9 MB in 64 requests on a phone: scripts 1.2 MB (41), images 318 KiB (6) and stylesheets 168 KiB (11). 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
Links must have discernible text (3 elements)
Links must have discernible text: 3 elements on the page fail this check, rated serious by axe-core.
Headings skip levels
Headings skip levels (h1 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 5 images in the HTML carry an alt attribute.
37 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 39 WCAG 2.2 A/AA and best-practice rules on the phone render: 37 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
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
Title is short (17 characters)
Your title is only 17 characters: “SAVVY SWAP EVENTS”. Between 30 and 65 characters leaves room to say what you do and for whom.
2 H1 headlines
There are 2 <h1> headlines (“Shop smarter. sell bigger. Be savvy.” and “UPCOMING EVENTS”). One clear main headline is easier for people and search engines.
Structured data has 1 problem
Structured data found (WebSite) but with 1 problem, for example “WebSite: image is not an absolute URL ("//images.squarespace-cdn.com/content/v1/69b9805774cc1b71757…”.
Open Graph partly set
Open Graph is missing og:description, so shared links fall back to guesses.
37 internal links, 2 external
The homepage links to 37 pages on lfakids.com and 2 external pages.
3 checks passed
Canonical URL set
The canonical URL is https://www.savvyswap.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://www.savvyswap.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.
No llms.txt
There is no https://www.savvyswap.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.
1 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.
Other pages
1 linked page is broken
Your homepage links to https://www.savvyswap.com/home, which answers with an error. Visitors hit a dead end and search engines drop it.
6 pages share 3 titles
https://www.savvyswap.com/savvy-swap-kids and https://www.savvyswap.com/shop all use the title “SHOP Savvy Kids — SAVVY SWAP EVENTS”, and 2 other titles repeat too. Search engines can't tell which page to show for a search, so each competes with the others.
10 pages without a meta description
https://www.savvyswap.com/savvy-swap-kids, https://www.savvyswap.com/savvy-style-home, https://www.savvyswap.com/savvy-swap-online, https://www.savvyswap.com/sell-with-savvy-kids, https://www.savvyswap.com/sell-at-style-home and https://www.savvyswap.com/savvy-online and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.
2 links to non-canonical URLs
Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://www.savvyswap.com/shop, whose canonical is https://www.savvyswap.com/savvy-swap-kids. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
2 pages without an H1
https://www.savvyswap.com/savvy-swap-online and https://www.savvyswap.com/savvy-online have no <h1> headline, so visitors and search engines get no clear main topic.
5 pages with very little text
https://www.savvyswap.com/savvy-swap-kids, https://www.savvyswap.com/savvy-style-home, https://www.savvyswap.com/savvy-online, https://www.savvyswap.com/contact and https://www.savvyswap.com/shop 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.
11 internal pages checked
We fetched 11 pages linked from your homepage and read each the way a search engine does.
2 checks passed
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 10 pages that loaded have a <title>.
Best practices
3 small tap targets
3 of 8 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.
1 checks passed
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.
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 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 58 words
The homepage has only about 58 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
2 checks passed
8 calls to action
The homepage has 8 calls to action, for example “SHOP”, “Contact Us” and “Folder: SHOP”.
Analytics in place
Analytics detected: Meta Pixel.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads Meta 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.
4 cookies set on arrival
4Opening the homepage sets 4 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.
9 other companies contacted
Loading the homepage contacts 9 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 lfakids.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
- Squarespace
- Hosting
- Squarespace
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 33 issues on lfakids.com, including 15 speed issues, 4 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.