Website review, no card needed
jlcandles.com.mx website review
Visit site (opens in a new tab)Reviewed 9 November 202633 issues · 73 checks
This review found 33 issues worth fixing on jlcandles.com.mx, 12 of them high impact, across 73 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
73C- #91,805 of 124,336 reviewed websitesbeats 23%
- #57,150 of 69,863 online storesbeats 15%
- #53,455 of 63,534 Shopify storesbeats 13%
Closest competitors among Shopify stores
Compare side by sideOne score from every part of this review. How it works
How it loaded on a phone
0.8 s
1.6 s
2.4 s
3.3 s
4.1 s
4.9 s
5.7 s
6.5 s
Speed
Improve image delivery
1.3 s · 467 KiB11 images could be 467 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.3 s 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.
Use efficient cache lifetimes
700 ms · 89 KiB7 files are served with short cache lifetimes, so returning visitors download them again (89 KiB).
Main-thread work: 2.6 s
A phone's processor spends 2.6 s on main-thread work while loading, 627 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
1,554 HTML elements
The page has 1,554 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Shopify adds 60 ms
60 msShopify costs a phone 60 ms of main-thread work and 501 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.
Reduce unused CSS
290 ms · 60 KiBAbout 60 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 290 ms faster on a phone.
Reduce unused JavaScript
210 ms · 52 KiBAbout 52 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 210 ms faster on a phone.
Legacy JavaScript
150 ms · 7 KiBPolyfills for old browsers add 7 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
4 third-party services on the page
4 third-party services load with your homepage (Shopify, nfcube.com and shop.app and others), adding 585 KiB and 85 ms of main-thread time.
1 long task on the main thread
1 long task block the main thread while loading, the longest for 93 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: 5 ms
5 msYour server sent the HTML in 5 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 9.7 s
9.7 sYour largest element takes 9.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 9.7 s
9.7 sThe page becomes fully interactive after 9.7 s. Good is under 3.8 s.
Speed Index: 6.1 s
6.1 sVisually, the page fills in at 6.1 s (Speed Index). Good is under 3.4 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.
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
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 43 ms
43 msScripts block the page for only 43 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 2.6 MB in 371 requests
2.6 MBYour homepage downloads 2.6 MB in 371 requests on a phone: other files 1.2 MB (182), scripts 626 KiB (146) and images 547 KiB (14). Under 2 MB keeps phones on slow connections fast.
About 0.7 g of CO₂ per visit
0.73 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.73 g of CO₂e: 87.4 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
9 text elements with low contrast
9 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Scrollable region must have keyboard access (4 elements)
Scrollable region must have keyboard access: 4 elements on the page fail this check, rated serious by axe-core.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
4 images without alt text
4 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (11 elements)
All page content should be contained by landmarks: 11 elements on the page fail 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.
ARIA role should be appropriate for the element (1 element)
ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
48 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 7 failed. 3 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 (10 characters)
Your title is only 10 characters: “JL CANDLES”. Between 30 and 65 characters leaves room to say what you do and for whom.
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
51 internal links, 8 external
The homepage links to 51 pages on jlcandles.com.mx and 8 external pages.
6 checks passed
One H1 headline
Your main headline reads: “JL CANDLES”.
Canonical URL set
The canonical URL is https://jlcandles.com.mx/.
Structured data in place
Structured data found: Organization.
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://jlcandles.com.mx/sitemap.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
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.
Text is in the HTML
Your server sends the page's text in the HTML (454 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://jlcandles.com.mx/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a title
https://jlcandles.com.mx/customer_authentication/redirect has no <title>, so Google invents the link text in results.
1 linked page hidden from search
https://jlcandles.com.mx/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
6 pages without a meta description
https://jlcandles.com.mx/collections, https://jlcandles.com.mx/customer_authentication/redirect, https://jlcandles.com.mx/collections/all, https://jlcandles.com.mx/collections/coleccion-de-yeso, https://jlcandles.com.mx/collections/velas-religiosas and https://jlcandles.com.mx/collections/bouquets have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages share a meta description
https://jlcandles.com.mx/products/bouquet-virgencita-plis-copia and https://jlcandles.com.mx/products/bouquet-tulipanes use the same meta description. A description written for each page earns more clicks.
3 pages without an H1
https://jlcandles.com.mx/pages/preguntas-frecuentes, https://jlcandles.com.mx/pages/contact and https://jlcandles.com.mx/customer_authentication/redirect have no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 28 found) and read each the way a search engine does.
3 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.
Best practices
18 small tap targets
18 of 36 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 “Failed to load resource: net::ERR_FAILED”.
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 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 analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
Phone number is not tap-to-call
Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.
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 701 words of copy
The homepage carries about 701 words of visible text.
2 checks passed
6 short forms
6 short forms (1 field at most) are right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 1 testimonial or review block and a star rating.
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.
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.
11 other companies contacted
Loading the homepage contacts 11 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 jlcandles.com.mx, 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 5 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
King Product Options · Judge Me Reviews · Instafeed · Mintt Tiktok Feed · Hulk Product Options
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 33 issues on jlcandles.com.mx, including 10 speed issues, 3 SEO issues and 3 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.