Website review, no card needed
j-landa.com website review
Visit site (opens in a new tab)Reviewed 5 November 202626 issues · 67 checks
This review found 26 issues worth fixing on j-landa.com, 7 of them high impact, across 67 checks. The most urgent: use efficient cache lifetimes. 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
76CClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
Speed
Use efficient cache lifetimes
3.3 s · 1.3 MB71 files are served with short cache lifetimes, so returning visitors download them again (1.3 MB).
Render-blocking requests
1.1 s12 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.
Mobile performance score: 72
72/100Your mobile performance score is 72. Pages that score under 90 lose visitors before the first paint.
Improve image delivery
300 ms · 652 KiB36 images could be 652 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.
2,426 HTML elements
The page has 2,426 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
1 long task on the main thread
1 long task block the main thread while loading, the longest for 51 ms. During a long task the page ignores taps.
Reduce unused JavaScript
21 KiBAbout 21 KiB of JavaScript is downloaded but never used on this page.
Reduce unused CSS
20 KiBAbout 20 KiB of CSS is downloaded but never applied on this page.
3 third-party services on the page
3 third-party services load with your homepage (Cloudflare, Google Fonts and Gravatar), adding 57 KiB and 10 ms of main-thread time.
Legacy JavaScript
10 KiBPolyfills for old browsers add 10 KiB JavaScript that modern phones do not need.
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: 0.5 s
A phone's processor spends 0.5 s on main-thread work while loading, 116 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: 6.4 s
6.4 sYour largest element takes 6.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Corporate Hampers”.
Speed Index: 5.2 s
5.2 sVisually, the page fills in at 5.2 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 6.4 s
6.4 sThe page becomes fully interactive after 6.4 s. Good is under 3.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.
3 checks passed
First Contentful Paint: 1.7 s
1.7 sThe first text or image appears after 1.7 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.001
0.001The layout barely moves while loading (CLS 0.001, good is under 0.1).
Total Blocking Time: 1 ms
1 msScripts block the page for only 1 ms while loading. Good is under 200 ms.
Images and page weight
15 images in older formats
15 images (1.3 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.
7 images far larger than shown
318 KiB7 images are downloaded at several times the size a phone draws them, for example Luxury-Corporate-Hampers1-1380x640.jpg at 1,380 px wide, shown at 366 px. Resized copies would save about 318 KiB.
5 images below the first screen load straight away
5 images further down the page (422 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 0.5 g of CO₂ per visit
0.55 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.55 g of CO₂e: 65.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Page weight: 1.9 MB in 76 requests
1.9 MBYour homepage downloads 1.9 MB in 76 requests on a phone: images 1.7 MB (53), scripts 104 KiB (9) and stylesheets 53 KiB (10). That is a lean page.
Accessibility
ARIA attributes must conform to valid values (4 elements)
ARIA attributes must conform to valid values: 4 elements on the page fail this check, rated critical by axe-core.
ARIA commands must have an accessible name (1 element)
ARIA commands must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.
All page content should be contained by landmarks (116 elements)
All page content should be contained by landmarks: 116 elements on the page fail this check, rated moderate by axe-core.
14 links without text
14 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h1 → h5, h4 → h6 and h2 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 108 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 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 5 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Meta description is short (50 characters)
Your meta description is only 50 characters: “Artful Jewelry Inspired by Style, Culture & Travel”. 70 to 160 characters is enough to sell the click.
2 H1 headlines
There are 2 <h1> headlines (“J Landa” and “J Landa”). One clear main headline is easier for people and search engines.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
No XML sitemap
No XML sitemap at https://j-landa.com/sitemap_index.xml, so Google discovers your pages only by following links.
273 internal links, 1 external
The homepage links to 273 pages on j-landa.com and 1 external page.
4 checks passed
Title: 60 characters
Your title is a healthy 60 characters: “J Landa - Artful Jewelry Inspired by Style, Culture & Travel”.
Canonical URL set
The canonical URL is https://j-landa.com/.
Structured data in place
Structured data found: BreadcrumbList, CollectionPage and WebSite.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
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://j-landa.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 (1,909 words), so crawlers that don't run JavaScript still read it.
Other pages
1 page points its canonical at the homepage
https://j-landa.com/home declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.
1 linked page hidden from search
https://j-landa.com/privacy-policy 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://j-landa.com/about, https://j-landa.com/blog-2, https://j-landa.com/contact, https://j-landa.com/home, https://j-landa.com/privacy-policy and https://j-landa.com/services 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 63 found) and read each the way a search engine does.
4 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Titles are unique
Every page we checked has its own title.
Every page has an H1
Each page we checked has a main headline.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
179 small tap targets
179 of 239 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
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 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 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.
About 2,391 words of copy
The homepage carries about 2,391 words of visible text.
3 checks passed
4 calls to action
The homepage has 4 calls to action, for example “Contact”.
Social proof on the page
Social proof on the homepage: 8 customer or partner logos and 27 trust badges.
Analytics in place
Analytics detected: Cloudflare Web Analytics.
Privacy and tracking
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.
4 other companies contacted
Loading the homepage contacts 4 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 j-landa.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
- WordPress
- Framework
- jQuery
- Hosting
- Cloudflare
Company
- Headquarters
- Houston
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 26 issues on j-landa.com, including 8 speed issues, 4 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.