Website review, no card needed
litfarms.com website review
Visit site (opens in a new tab)Reviewed 19 November 202631 issues · 87 checks
This review found 31 issues worth fixing on litfarms.com, 9 of them high impact, across 87 checks. The most urgent: main-thread work: 27.9 s. 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
82B- #34,135 of 121,777 reviewed websitesbeats 66%
- #22,709 of 68,874 online storesbeats 61%
- #21,946 of 62,757 Shopify storesbeats 58%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 1.8 s |
| Jun 6, 2026 | 1.8 s |
| Jun 13, 2026 | 1.8 s |
| Jun 20, 2026 | 1.9 s |
| Jun 27, 2026 | 1.9 s |
| Jul 4, 2026 | 1.9 s |
| Jul 11, 2026 | 1.9 s |
| Jul 18, 2026 | 1.9 s |
| Jul 25, 2026 | 1.9 s |
| Aug 1, 2026 | 2.0 s |
| Aug 8, 2026 | 2.1 s |
| Aug 15, 2026 | 2.1 s |
| Aug 22, 2026 | 2.2 s |
| Aug 29, 2026 | 2.2 s |
| Sep 5, 2026 | 2.2 s |
| Sep 12, 2026 | 2.2 s |
| Sep 19, 2026 | 2.2 s |
| Sep 26, 2026 | 2.2 s |
| Oct 3, 2026 | 2.2 s |
| Oct 10, 2026 | 2.2 s |
| Oct 17, 2026 | 2.2 s |
| Oct 24, 2026 | 2.2 s |
| Oct 31, 2026 | 2.1 s |
| Nov 7, 2026 | 2.1 s |
| Nov 14, 2026 | 2.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 119 ms |
| Jun 6, 2026 | 122 ms |
| Jun 13, 2026 | 122 ms |
| Jun 20, 2026 | 121 ms |
| Jun 27, 2026 | 121 ms |
| Jul 4, 2026 | 122 ms |
| Jul 11, 2026 | 122 ms |
| Jul 18, 2026 | 127 ms |
| Jul 25, 2026 | 146 ms |
| Aug 1, 2026 | 173 ms |
| Aug 8, 2026 | 200 ms |
| Aug 15, 2026 | 225 ms |
| Aug 22, 2026 | 229 ms |
| Aug 29, 2026 | 228 ms |
| Sep 5, 2026 | 236 ms |
| Sep 12, 2026 | 237 ms |
| Sep 19, 2026 | 235 ms |
| Sep 26, 2026 | 236 ms |
| Oct 3, 2026 | 236 ms |
| Oct 10, 2026 | 236 ms |
| Oct 17, 2026 | 236 ms |
| Oct 24, 2026 | 237 ms |
| Oct 31, 2026 | 236 ms |
| Nov 7, 2026 | 238 ms |
| Nov 14, 2026 | 236 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
Speed
Main-thread work: 27.9 s
A phone's processor spends 27.9 s on main-thread work while loading, 2.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
3,018 HTML elements
The page has 3,018 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Use efficient cache lifetimes
1.8 MB28 files are served with short cache lifetimes, so returning visitors download them again (1.8 MB).
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, route.com and Shopify and others), adding 2.5 MB and 1.3 s of main-thread time.
Reduce unused JavaScript
1.4 MBAbout 1.4 MB of JavaScript is downloaded but never used on this page.
Mobile performance score: 69
69/100Your mobile performance score is 69. Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
900 ms16 files block the first paint until they finish downloading. Deferring or inlining them could save about 900 ms.
Improve image delivery
894 KiB14 images could be 894 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Google Tag Manager adds 521 ms
521 msGoogle Tag Manager costs a phone 521 ms of main-thread work and 602 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.
route.com adds 454 ms
454 msroute.com costs a phone 454 ms of main-thread work and 1.1 MB 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.
Duplicated JavaScript
510 KiB510 KiB JavaScript is shipped twice across bundles.
Shopify adds 115 ms
115 msShopify costs a phone 115 ms of main-thread work and 370 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.
instant.one adds 56 ms
56 msinstant.one costs a phone 56 ms of main-thread work and 299 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.
17 long tasks on the main thread
17 long tasks block the main thread while loading, the longest for 234 ms. During a long task the page ignores taps.
Reduce unused CSS
58 KiBAbout 58 KiB of CSS is downloaded but never applied on this page.
Legacy JavaScript
52 KiBPolyfills for old browsers add 52 KiB JavaScript that modern phones do not need.
Minify JavaScript
15 KiB15 KiB could be saved by minifying JavaScript.
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.
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: 81 ms
81 msYour server sent the HTML in 81 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.
Time to Interactive: 42.2 s
42.2 sThe page becomes fully interactive after 42.2 s. Good is under 3.8 s.
Total Blocking Time: 1.3 s
1.3 sScripts block taps and scrolling for 1.3 s in total while the page loads. Good is under 200 ms.
Speed Index: 6.5 s
6.5 sVisually, the page fills in at 6.5 s (Speed Index). Good is under 3.4 s.
Real-user INP: 270 ms
270 msReal visitors wait 270 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 97% slower for real visitors
+97%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 119 ms to 236 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 2.1 s
2.1 sReal visitors see the first content after 2.1 s (75th percentile). Good is under 1.8 s.
Largest content (LCP) got 15% slower for real visitors
+15%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 1.8 s to 2.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 checks passed
Real-user LCP: 2.5 s
2.5 sReal visitors wait 2.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user TTFB: 508 ms
508 msReal visitors wait 508 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 1.5 s
1.5 sThe first text or image appears after 1.5 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.005
0.005The layout barely moves while loading (CLS 0.005, good is under 0.1).
Largest Contentful Paint: 1.5 s
1.5 sYour largest element renders in 1.5 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Welcome to LIT Farms! Your insider access to top-shelf THCA…”.
Images and page weight
Page weight: 8.3 MB in 480 requests
8.3 MBYour homepage downloads 8.3 MB in 480 requests on a phone: scripts 2.8 MB (93), fonts 2.5 MB (21) and other files 1.4 MB (310). Under 2 MB keeps phones on slow connections fast.
3 images below the first screen load straight away
3 images further down the page (168 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 2.4 g of CO₂ per visit
2.37 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.37 g of CO₂e: 284.0 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
4 text elements with low contrast
4 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Headings skip levels
Headings skip levels (h2 → h5), which makes the page harder to scan with a screen reader.
1 checks passed
Every image has alt text
All 36 images in the HTML carry an alt attribute.
SEO
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
108 internal links, 2 external
The homepage links to 108 pages on litfarms.com and 2 external pages.
7 checks passed
Meta description: 80 characters
Your meta description is 80 characters: “Top THCa vendor with stunning quality, unrivaled value and extensive experience.”.
One H1 headline
Your main headline reads: “LIT FARMS”.
Title: 58 characters
Your title is a healthy 58 characters: “Lost In Translation - High-Quality THCa Vendor | Lit Farms”.
Canonical URL set
The canonical URL is https://litfarms.com/.
Structured data in place
Structured data found: BreadcrumbList, Organization, Store and WebSite.
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://litfarms.com/sitemap.xml.
AI search readiness
No llms.txt
There is no https://litfarms.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.
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: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
Text is in the HTML
Your server sends the page's text in the HTML (1,290 words), so crawlers that don't run JavaScript still read it.
Other pages
3 pages slow to respond
https://litfarms.com/collections/preferred, https://litfarms.com/collections/supreme and https://litfarms.com/collections/smalls-thca-flower took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 54 found) and read each the way a search engine does.
7 checks passed
Linked pages load
6 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.
Every page has a meta description
All 6 pages that loaded have a meta description.
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 6 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 (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_TUNNEL_CONNECTION_FAILED”.
Pasting is blocked
A form field blocks pasting, which frustrates password managers and people on phones.
2 checks passed
Tap targets are thumb-sized
49 of 49 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 phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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 917 words of copy
The homepage carries about 917 words of visible text.
6 checks passed
6 calls to action
The homepage has 6 calls to action, for example “Shop Now” and “Contact information”.
35 short forms
35 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
Opening hours shown
Your opening hours are on the homepage.
LocalBusiness structured data
Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and X (Twitter) Ads (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
24Opening the homepage sets 24 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.
43 other companies contacted
Loading the homepage contacts 43 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 litfarms.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 18 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Triplewhale · Tinyseo Seo Speed · Gorgias Live Chat Helpdesk · Uppromote Affiliate · Klaviyo Email Marketing Sms · Route Protection Tracking · Judge Me Reviews · Powerful Form Builder · Thoughtmetric · Affliate By Secomapp · Stape Remix · Variable Products · metorik.com · ablestar.app · cloudfront.net · good-apps.co · kount.com · instant.one
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
- Analytics
- Google Tag Manager
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 31 issues on litfarms.com, including 20 speed issues, 2 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.