Website review, no card needed
rusticburl.com website review
Visit site (opens in a new tab)Reviewed 12 November 202620 issues · 74 checks
This review found 20 issues worth fixing on rusticburl.com, 8 of them high impact, across 74 checks. The most urgent: reduce unused JavaScript. 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
84B- #19,094 of 105,045 reviewed websitesbeats 77%
- #12,320 of 58,944 online storesbeats 73%
- #11,959 of 53,701 Shopify storesbeats 71%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 904 ms |
| May 30, 2026 | 916 ms |
| Jun 6, 2026 | 873 ms |
| Jun 13, 2026 | 914 ms |
| Jun 20, 2026 | 914 ms |
| Jun 27, 2026 | 966 ms |
| Jul 4, 2026 | 999 ms |
| Jul 11, 2026 | 1.1 s |
| Jul 18, 2026 | 1.0 s |
| Jul 25, 2026 | 942 ms |
| Aug 1, 2026 | 861 ms |
| Aug 8, 2026 | 834 ms |
| Aug 15, 2026 | 884 ms |
| Aug 29, 2026 | 1.0 s |
| Sep 5, 2026 | 1.1 s |
| Sep 12, 2026 | 970 ms |
| Sep 26, 2026 | 1.0 s |
| Oct 3, 2026 | 1.0 s |
| Oct 10, 2026 | 1.0 s |
| Oct 17, 2026 | 1.0 s |
| Oct 24, 2026 | 909 ms |
| Oct 31, 2026 | 871 ms |
| Nov 7, 2026 | 887 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 101 ms |
| May 30, 2026 | 95 ms |
| Jun 6, 2026 | 86 ms |
| Jun 13, 2026 | 92 ms |
| Jun 20, 2026 | 79 ms |
| Jun 27, 2026 | 79 ms |
| Jul 4, 2026 | 73 ms |
| Jul 11, 2026 | 79 ms |
| Jul 18, 2026 | 83 ms |
| Jul 25, 2026 | 87 ms |
| Aug 1, 2026 | 92 ms |
| Aug 15, 2026 | 92 ms |
| Oct 3, 2026 | 96 ms |
| Oct 17, 2026 | 101 ms |
| Oct 24, 2026 | 105 ms |
| Nov 7, 2026 | 105 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
Reduce unused JavaScript
1.2 s · 251 KiBAbout 251 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.2 s faster on a phone.
Mobile performance score: 67
67/100Your mobile performance score is 67. Pages that score under 90 lose visitors before the first paint.
6 third-party services on the page
6 third-party services load with your homepage (Shopify, Klaviyo and 506.io and others), adding 849 KiB and 519 ms of main-thread time.
Improve image delivery
300 ms · 202 KiB6 images could be 202 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.
Shopify adds 370 ms
370 msShopify costs a phone 370 ms of main-thread work and 502 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.
Legacy JavaScript
250 ms · 49 KiBPolyfills for old browsers add 49 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 250 ms faster on a phone.
Use efficient cache lifetimes
150 ms · 19 KiB5 files are served with short cache lifetimes, so returning visitors download them again (19 KiB).
1 long task on the main thread
1 long task block the main thread while loading, the longest for 77 ms. During a long task the page ignores taps.
Reduce unused CSS
11 KiBAbout 11 KiB of CSS is downloaded but never applied on this page.
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.
Minify JavaScript
4 KiB4 KiB could be saved by minifying JavaScript.
2 checks passed
Main-thread work: 1.6 s
A phone's processor spends 1.6 s on main-thread work while loading, 804 ms of it running JavaScript. That is comfortably low.
Server response: 8 ms
8 msYour server sent the HTML in 8 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 10.0 s
10.0 sYour largest element takes 10.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 10.0 s
10.0 sThe page becomes fully interactive after 10.0 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.3 s
2.3 sThe first text or image appears after 2.3 s on a phone. Good is under 1.8 s.
Tap response (INP) held steady for real visitors
+7%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 101 ms to 105 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-3%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 0.9 s to 0.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 1.0 s
1.0 sReal visitors wait 1.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 104 ms
104 msReal visitors wait 104 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.0 s
1.0 sReal visitors see the first content after 1.0 s (75th percentile). Good is under 1.8 s.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 27 ms
27 msScripts block the page for only 27 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 2.3 MB in 212 requests
2.3 MBYour homepage downloads 2.3 MB in 212 requests on a phone: scripts 881 KiB (94), other files 774 KiB (85) and images 496 KiB (10). Under 2 MB keeps phones on slow connections fast.
1 image in older formats
1 image (39 KiB) is 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.
About 0.6 g of CO₂ per visit
0.65 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.65 g of CO₂e: 77.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
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
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
5 images without alt text
5 images have no alt text, which hurts accessibility and image search.
1 checks passed
48 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: 48 passed and 2 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (17 characters)
Your title is only 17 characters: “Rustic Burl & Co.”. Between 30 and 65 characters leaves room to say what you do and for whom.
Meta description is short (33 characters)
Your meta description is only 33 characters: “Quality Wood Products For Artists”. 70 to 160 characters is enough to sell the click.
2 H1 headlines
There are 2 <h1> headlines (“” and “Frames and panels, built by hand for artists.”). One clear main headline is easier for people and search engines.
89 internal links, 7 external
The homepage links to 89 pages on rusticburl.com and 7 external pages.
5 checks passed
Canonical URL set
The canonical URL is https://rusticburl.com/.
Structured data in place
Structured data found: Organization and WebSite.
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://rusticburl.com/sitemap.xml.
AI search readiness
4 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 (921 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://rusticburl.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
4 pages share a meta description
https://rusticburl.com/collections/panels and https://rusticburl.com/collections/frames use the same meta description. A description written for each page earns more clicks.
4 pages slow to respond
https://rusticburl.com/products/cradled-panels, https://rusticburl.com/products/round-floater-panels, https://rusticburl.com/products/ovals and https://rusticburl.com/products/float-frames-for-uncradled-panels took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 29 found) and read each the way a search engine does.
7 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.
Every page has a meta description
All 15 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 15 pages that loaded have a <title>.
Best practices
1 broken image
1 image failed to load on a phone, for example https://rusticburl.com/.
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
10 of 10 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 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 536 words of copy
The homepage carries about 536 words of visible text.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Shop frames” and “Shop panels”.
16 calls to action
The homepage has 16 calls to action, for example “Shop All”, “Contact Us” and “Artist Sign Up”.
5 short forms
5 short forms (1 field at most) are right on the homepage.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager, Klaviyo and 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.
13 cookies set on arrival
13Opening the homepage sets 13 cookies, 1 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.
16 other companies contacted
Loading the homepage contacts 16 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 rusticburl.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 4 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Aris Product Options · Sami Wholesale · Klaviyo Email Marketing Sms · Eg Auto Add To Cart
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
- jQuery
- 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 20 issues on rusticburl.com, including 9 speed issues, 3 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.