Website review, no card needed
bringtheloves.com website review
Visit site (opens in a new tab)Reviewed 10 November 202630 issues · 69 checks
This review found 30 issues worth fixing on bringtheloves.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.2 s · 305 KiBAbout 305 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.2 s faster on a phone.
Use efficient cache lifetimes
1.4 s · 283 KiB12 files are served with short cache lifetimes, so returning visitors download them again (283 KiB).
Improve image delivery
750 ms · 542 KiB10 images could be 542 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 750 ms faster on a phone.
Mobile performance score: 59
59/100Your mobile performance score is 59. Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
900 ms3 files block the first paint until they finish downloading. Deferring or inlining them could save about 900 ms.
Legacy JavaScript
300 ms · 42 KiBPolyfills for old browsers add 42 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.
PayPal adds 266 ms
266 msPayPal costs a phone 266 ms of main-thread work and 393 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.
1,535 HTML elements
The page has 1,535 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
8 third-party services on the page
8 third-party services load with your homepage (PayPal, Shopify and reddit and others), adding 702 KiB and 351 ms of main-thread time.
4 long tasks on the main thread
4 long tasks block the main thread while loading, the longest for 130 ms. During a long task the page ignores taps.
Reduce unused CSS
13 KiBAbout 13 KiB of CSS is downloaded but never applied on this page.
Minify CSS
6 KiB6 KiB could be saved by minifying CSS.
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.
2 checks passed
Main-thread work: 1.6 s
A phone's processor spends 1.6 s on main-thread work while loading, 778 ms of it running JavaScript. That is comfortably low.
Server response: 7 ms
7 msYour server sent the HTML in 7 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 10.8 s
10.8 sYour largest element takes 10.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
First Contentful Paint: 5.3 s
5.3 sThe first text or image appears after 5.3 s on a phone. Good is under 1.8 s.
Time to Interactive: 10.9 s
10.9 sThe page becomes fully interactive after 10.9 s. Good is under 3.8 s.
Speed Index: 7.0 s
7.0 sVisually, the page fills in at 7.0 s (Speed Index). Good is under 3.4 s.
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.
2 checks passed
Cumulative Layout Shift: 0.003
0.003The layout barely moves while loading (CLS 0.003, good is under 0.1).
Total Blocking Time: 61 ms
61 msScripts block the page for only 61 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 2.4 MB in 182 requests
2.4 MBYour homepage downloads 2.4 MB in 182 requests on a phone: images 815 KiB (14), other files 787 KiB (90) and scripts 547 KiB (44). Under 2 MB keeps phones on slow connections fast.
1 image far larger than shown
35 KiB1 image is downloaded at several times the size a phone draws it, for example BringTheLove_Family_Banner_38ec3c40-44d9-405f-9a80-5be91269b at 1,600 px wide, shown at 390 px. Resized copies would save about 35 KiB.
About 0.7 g of CO₂ per visit
0.69 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.69 g of CO₂e: 82.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 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.
Accessibility
8 text elements with low contrast
8 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Alternative text of images should not be repeated as text (5 elements)
Alternative text of images should not be repeated as text: 5 elements on the page fail this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 16 images in the HTML carry an alt attribute.
50 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 2 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (14 characters)
Your title is only 14 characters: “Bring The Love”. Between 30 and 65 characters leaves room to say what you do and for whom.
Canonical points to another host
Your canonical URL points to bringthelove.com, not bringtheloves.com, so Google may credit that host instead.
Meta description is short (56 characters)
Your meta description is only 56 characters: “For all the ways and in all the moments, Bring The Love!”. 70 to 160 characters is enough to sell the click.
Structured data has 1 problem
Structured data found (Organization, Product and WebSite) but with 1 problem, for example “Organization: url points at a different host (https://bringthelove.com)”.
One H1 headline
Your <h1> is empty.
53 internal links, 6 external
The homepage links to 53 pages on bringtheloves.com and 6 external pages.
3 checks passed
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://bringtheloves.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 (950 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://bringtheloves.com/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://bringtheloves.com/collections/wife-1, https://bringtheloves.com/collections/son-1, https://bringtheloves.com/collections/daughter-1, https://bringtheloves.com/collections/mom-2, https://bringtheloves.com/collections/dad and https://bringtheloves.com/collections/girlfriend-1 and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 25 found) and read each the way a search engine does.
6 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.
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
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 400 ()”.
No HTML doctype
The page has no <!DOCTYPE html>, so browsers render it in quirks mode.
2 checks passed
Tap targets are thumb-sized
20 of 20 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.
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.
Only about 205 words
The homepage has only about 205 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.
3 checks passed
2 calls to action
The homepage has 2 calls to action, for example “Shop By Recipient” and “Shop By Event”.
6 short forms
6 short forms (1 field at most) are right on the homepage.
Direct contact links
Visitors can reach you directly: 1 phone link and 1 email link.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager, Meta Pixel, Reddit 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.
20 cookies set on arrival
20Opening the homepage sets 20 cookies, 2 of them by other companies (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.
27 other companies contacted
Loading the homepage contacts 27 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 bringtheloves.com, 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
Kaching Bundles
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 30 issues on bringtheloves.com, including 12 speed issues, 5 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.