Website review, no card needed

nowlovers.com logo

nowlovers.com website review

Visit site (opens in a new tab)Reviewed 9 November 202630 issues · 72 checks

This review found 30 issues worth fixing on nowlovers.com, 11 of them high impact, across 72 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Full-page screenshot of nowlovers.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. nowlovers.com at 0.6 s0.6 s
  2. nowlovers.com at 1.2 s1.2 s
  3. nowlovers.com at 1.8 s1.8 s
  4. nowlovers.com at 2.5 s2.5 s
  5. nowlovers.com at 3.1 s3.1 s
  6. nowlovers.com at 3.7 s3.7 s
  7. nowlovers.com at 4.3 s4.3 s
  8. nowlovers.com at 4.9 s4.9 s

Speed

8 to fix62
  • Reduce unused JavaScript

    1.9 s · 284 KiB

    About 284 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.9 s faster on a phone.

  • Use efficient cache lifetimes

    950 ms · 151 KiB

    19 files are served with short cache lifetimes, so returning visitors download them again (151 KiB).

  • Mobile performance score: 62

    62/100

    Your mobile performance score is 62. Pages that score under 90 lose visitors before the first paint.

  • Render-blocking requests

    650 ms

    3 files block the first paint until they finish downloading. Deferring or inlining them could save about 650 ms.

  • Reduce unused CSS

    610 ms · 40 KiB

    About 40 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 610 ms faster on a phone.

  • Improve image delivery

    400 ms · 132 KiB

    3 images could be 132 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 400 ms faster on a phone.

  • Main-thread work: 2.5 s

    A phone's processor spends 2.5 s on main-thread work while loading, 1.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • 2,060 HTML elements

    The page has 2,060 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 (Shopify, omnisnippet1.com and Klaviyo and others), adding 644 KiB and 326 ms of main-thread time.

  • Legacy JavaScript

    200 ms · 31 KiB

    Polyfills for old browsers add 31 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.

  • 2 long tasks on the main thread

    2 long tasks block the main thread while loading, the longest for 196 ms. During a long task the page ignores taps.

  • 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.

1 checks passed
  • Server response: 8 ms

    8 ms

    Your server sent the HTML in 8 ms, well inside Google's 600 ms guideline.

Core Web Vitals

4 to fix65
  • Largest Contentful Paint: 11.7 s

    11.7 s

    Your largest element takes 11.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

  • Time to Interactive: 11.7 s

    11.7 s

    The page becomes fully interactive after 11.7 s. Good is under 3.8 s.

  • First Contentful Paint: 3.3 s

    3.3 s

    The first text or image appears after 3.3 s on a phone. Good is under 1.8 s.

  • Speed Index: 6.4 s

    6.4 s

    Visually, the page fills in at 6.4 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
  • Total Blocking Time: 148 ms

    148 ms

    Scripts block the page for only 148 ms while loading. Good is under 200 ms.

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

1 to fix85
  • Page weight: 2.3 MB in 182 requests

    2.3 MB

    Your homepage downloads 2.3 MB in 182 requests on a phone: scripts 822 KiB (80), other files 662 KiB (77) and images 580 KiB (10). Under 2 MB keeps phones on slow connections fast.

  • 1 image below the first screen load straight away

    1 image further down the page (54 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 0.6 g of CO₂ per visit

    0.64 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.64 g of CO₂e: 76.7 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 are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

5 to fixGoogle 9092
  • Hidden but focusable

    1 element hidden from screen readers can still receive keyboard focus.

  • ARIA toggle fields must have an accessible name (1 element)

    ARIA toggle fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

  • Interactive controls must not be nested (1 element)

    Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

  • All page content should be contained by landmarks (6 elements)

    All page content should be contained by landmarks: 6 elements on the page fail this check, rated moderate by axe-core.

  • 22 links without text

    22 visible links have no text or label, so screen readers cannot say where they go.

  • Headings skip levels

    Headings skip levels (h2 → h4 and h4 → h6), which makes the page harder to scan with a screen reader.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

2 checks passed
  • Every image has alt text

    All 64 images in the HTML carry an alt attribute.

  • 47 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 6 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 10082
  • Canonical points to another host

    Your canonical URL points to now.com.pe, not nowlovers.com, so Google may credit that host instead.

  • 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 long (238 characters)

    Your meta description is 238 characters; Google truncates after about 160, so the end of your pitch is cut.

  • One H1 headline

    Your <h1> is empty.

  • 305 internal links, 122 external

    The homepage links to 305 pages on nowlovers.com and 122 external pages.

4 checks passed
  • Title: 55 characters

    Your title is a healthy 55 characters: “NOW® │ Tienda de Ropa, Accesorios y más – 🇵🇪 Now Peru”.

  • 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://nowlovers.com/sitemap.xml.

AI search readiness

1 to fix88
  • 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://nowlovers.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.

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.

  • Text is in the HTML

    Your server sends the page's text in the HTML (802 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix95
  • 7 pages without a meta description

    https://nowlovers.com/collections/nueva-coleccion, https://nowlovers.com/collections/nueva-coleccion-ropa, https://nowlovers.com/collections/nueva-coleccion-accesorios, https://nowlovers.com/collections/bestsellers-ropa, https://nowlovers.com/collections/nite-out and https://nowlovers.com/collections/nueva-coleccion-tops and 1 other 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 79 found) and read each the way a search engine does.

6 checks passed
  • Linked pages load

    7 pages of 15 loaded without an error (the rest turned automated requests away).

  • 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 7 pages that loaded have a <title>.

Best practices

Google 96100
  • Requests the notification permission on page load

    Requests the notification permission on page load.

3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    25 of 30 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix33
  • 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 328 words of copy

    The homepage carries about 328 words of visible text.

1 checks passed
  • 4 short forms

    4 short forms (1 field at most) are right on the homepage, asking for an email.

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 1 more (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.

  • 24 cookies set on arrival

    24

    Opening the homepage sets 24 cookies, 4 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.

  • 31 other companies contacted

    Loading the homepage contacts 31 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 nowlovers.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 11 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Hulk Form Builder · Mercado Pago Antifraud Plus · Judge Me Reviews · Klaviyo Email Marketing Sms · Omnisend · Event Promotion Bar · Mercadopago Pf App · Free Shipping Bar · Selleasy · Whatsapp Chat · hextom.com

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
Bootstrap
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 nowlovers.com, including 12 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25