Website review, no card needed

nexluma.shop logo

nexluma.shop website review

Visit site (opens in a new tab)Reviewed 11 November 202643 issues · 82 checks

This review found 43 issues worth fixing on nexluma.shop, 17 of them high impact, across 82 checks. The most urgent: use efficient cache lifetimes. 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 nexluma.shop (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. nexluma.shop at 0.4 s0.4 s
  2. nexluma.shop at 0.8 s0.8 s
  3. nexluma.shop at 1.3 s1.3 s
  4. nexluma.shop at 1.7 s1.7 s
  5. nexluma.shop at 2.1 s2.1 s
  6. nexluma.shop at 2.5 s2.5 s
  7. nexluma.shop at 3.0 s3.0 s
  8. nexluma.shop at 3.4 s3.4 s

Speed

12 to fix49
  • Use efficient cache lifetimes

    3.8 s · 2.2 MB

    82 files are served with short cache lifetimes, so returning visitors download them again (2.2 MB).

  • Render-blocking requests

    4.5 s

    23 files block the first paint until they finish downloading. Deferring or inlining them could save about 4.5 s.

  • Reduce unused JavaScript

    1.5 s · 953 KiB

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

  • Mobile performance score: 49

    49/100

    Your mobile performance score is 49. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Facebook, Google Maps and Accessibe Accessibility Overlay and others), adding 1.5 MB and 945 ms of main-thread time.

  • Improve image delivery

    450 ms · 545 KiB

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

  • Reduce unused CSS

    600 ms · 56 KiB

    About 56 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.

  • Font display

    550 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 550 ms).

  • Legacy JavaScript

    350 ms · 40 KiB

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

  • Facebook adds 278 ms

    278 ms

    Facebook costs a phone 278 ms of main-thread work and 284 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.

  • Main-thread work: 3.0 s

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

  • Google Maps adds 165 ms

    165 ms

    Google Maps costs a phone 165 ms of main-thread work and 394 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.

  • 9 long tasks on the main thread

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

  • Minify JavaScript

    6 KiB

    6 KiB could be saved by minifying JavaScript.

  • 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: 159 ms

    159 ms

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

Core Web Vitals

6 to fix56
  • Largest Contentful Paint: 10.2 s

    10.2 s

    Your largest element takes 10.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Promotional image for a holiday gift guide with pet toys an…”.

  • Time to Interactive: 22.3 s

    22.3 s

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

  • First Contentful Paint: 4.8 s

    4.8 s

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

  • Speed Index: 7.8 s

    7.8 s

    Visually, the page fills in at 7.8 s (Speed Index). Good is under 3.4 s.

  • Total Blocking Time: 388 ms

    388 ms

    Scripts block taps and scrolling for 388 ms in total while the page loads. Good is under 200 ms.

  • 7 images without width and height

    7 images 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.003

    0.003

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

Images and page weight

4 to fix43
  • Page weight: 5.5 MB in 228 requests

    5.5 MB

    Your homepage downloads 5.5 MB in 228 requests on a phone: scripts 2.3 MB (78), images 1.6 MB (36) and other files 1.4 MB (99). Under 2 MB keeps phones on slow connections fast.

  • 23 images in older formats

    23 images (1.6 MB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

  • 12 images below the first screen load straight away

    12 images further down the page (405 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 1 image far larger than shown

    21 KiB

    1 image is downloaded at several times the size a phone draws it, for example MB30-Carousel.jpg at 1,200 px wide, shown at 370 px. Resized copies would save about 21 KiB.

  • About 1.6 g of CO₂ per visit

    1.56 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.56 g of CO₂e: 186.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Accessibility

9 to fixGoogle 7387
  • 6 buttons without a name

    6 buttons have no accessible name, so screen readers announce just “button”.

  • 7 tap targets too small

    7 tap targets are too small or too close together to hit reliably with a finger.

  • 2 text elements with low contrast

    2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 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 (4 elements)

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

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

  • 2 links without text

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

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • Headings skip levels

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

1 checks passed
  • 42 automated accessibility rules passed

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

SEO

2 to fixGoogle 9285
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Meta description is long (289 characters)

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

  • 95 internal links, 9 external

    The homepage links to 95 pages on nexluma.shop and 9 external pages.

6 checks passed
  • Title: 60 characters

    Your title is a healthy 60 characters: “Natural Pet Store Products & Supplies | Shop Kriser's Online”.

  • Canonical URL set

    The canonical URL is https://nexluma.shop/.

  • Structured data in place

    Structured data found: Corporation.

  • 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.krisers.com/sitemapindex.xml.

AI search readiness

100
  • No llms.txt

    There is no https://nexluma.shop/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.

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.

  • 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 (522 words), so crawlers that don't run JavaScript still read it.

Other pages

4 to fix50
  • 3 linked pages are broken

    Your homepage links to https://nexluma.shop/collections/best-sellers, https://nexluma.shop/a/pages/offers and https://nexluma.shop/a/pages/services, which answer with an error. Visitors hit a dead end and search engines drop them.

  • 1 page without a title

    https://nexluma.shop/collections/cat/litter-accessories has no <title>, so Google invents the link text in results.

  • 1 page without a meta description

    https://nexluma.shop/collections/cat/litter-accessories has no meta description, so Google writes the search snippet from whatever text it finds.

  • 5 pages without an H1

    https://nexluma.shop/collections/all, https://nexluma.shop/collections/new-products, https://nexluma.shop/collections/dog-supplies, https://nexluma.shop/collections/cat/litter-accessories and https://nexluma.shop/collections/cat-supplies have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page slow to respond

    https://nexluma.shop/pages/foodfinder took over 3 s to send its HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 60 found) and read each the way a search engine does.

3 checks passed
  • 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.

Best practices

4 to fixGoogle 8575
  • 13 small tap targets

    13 of 57 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • Scrolls sideways on phones

    On a 390 px-wide phone the page scrolls sideways, a sign that something is wider than the screen.

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “asyncLoad is not defined”.

  • No HTML doctype

    The page has no <!DOCTYPE html>, so browsers render it in quirks mode.

  • Requests the geolocation permission on page load

    Requests the geolocation permission on page load.

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix75
  • 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: 15 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

  • 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 363 words of copy

    The homepage carries about 363 words of visible text.

4 checks passed
  • 8 calls to action

    The homepage has 8 calls to action, for example “Join Rewards”, “Shop” and “SHOP BOWLS”.

  • 8 short forms

    8 short forms (2 fields at most) are right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics, Meta Pixel and Cloudflare Web Analytics.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 0 email links.

Privacy and tracking

  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads Meta Pixel, Microsoft Ads and Pinterest Tag (measured from a US location before any click). A consent tool (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.

  • 14 cookies set on arrival

    14

    Opening the homepage sets 14 cookies (measured from a US location before any click).

  • 40 other companies contacted

    Loading the homepage contacts 40 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • Consent tool: CookieYes

    A consent management tool (CookieYes) loads with the page.

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 nexluma.shop, 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 13 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Cookieyes Gdpr Cookie Banner · Hulk Form Builder · Minmaxify Order Limits · Mntn · Inbox · Astro Loyalty Shopify · Smartmenu · privy.com · cloudfront.net · nofraud.com · shgcdn3.com · yotpo.com · Qikify

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

  • The footer still says © 2025.

Stack

Framework
Astro
E-commerce
Shopify
Analytics
Google Analytics | Google Tag Manager
Hosting
Cloudflare

Hiring

Hiring
12 open roles
Job board
paylocity

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 43 issues on nexluma.shop, including 18 speed issues, 2 SEO issues and 2 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