Website review, no card needed
berings.com website review
Visit site (opens in a new tab)Reviewed 22 October 202629 issues · 78 checks
This review found 29 issues worth fixing on berings.com, 6 of them high impact, across 78 checks. The most urgent: fails Core Web Vitals for real visitors. 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
75C- #72,870 of 110,322 reviewed websitesbeats 30%
- #46,514 of 62,689 online storesbeats 22%
- #1,224 of 2,537 WooCommerce storesbeats 45%
Closest competitors among WooCommerce stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 2.8 s |
| May 9, 2026 | 2.8 s |
| May 16, 2026 | 2.7 s |
| May 23, 2026 | 2.8 s |
| May 30, 2026 | 2.9 s |
| Jun 6, 2026 | 2.8 s |
| Jun 13, 2026 | 2.9 s |
| Jun 20, 2026 | 2.9 s |
| Jun 27, 2026 | 2.9 s |
| Jul 4, 2026 | 3.0 s |
| Jul 11, 2026 | 2.9 s |
| Jul 18, 2026 | 2.9 s |
| Jul 25, 2026 | 2.9 s |
| Aug 1, 2026 | 2.9 s |
| Aug 8, 2026 | 3.0 s |
| Aug 15, 2026 | 3.1 s |
| Aug 22, 2026 | 2.9 s |
| Aug 29, 2026 | 2.9 s |
| Sep 5, 2026 | 2.7 s |
| Sep 12, 2026 | 2.7 s |
| Sep 19, 2026 | 2.7 s |
| Sep 26, 2026 | 2.7 s |
| Oct 3, 2026 | 2.7 s |
| Oct 10, 2026 | 2.8 s |
| Oct 17, 2026 | 2.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 111 ms |
| May 9, 2026 | 110 ms |
| May 16, 2026 | 105 ms |
| May 23, 2026 | 105 ms |
| May 30, 2026 | 107 ms |
| Jun 6, 2026 | 111 ms |
| Jun 13, 2026 | 112 ms |
| Jun 20, 2026 | 117 ms |
| Jun 27, 2026 | 117 ms |
| Jul 4, 2026 | 112 ms |
| Jul 11, 2026 | 112 ms |
| Jul 18, 2026 | 106 ms |
| Jul 25, 2026 | 102 ms |
| Aug 1, 2026 | 101 ms |
| Aug 8, 2026 | 101 ms |
| Aug 15, 2026 | 104 ms |
| Aug 22, 2026 | 104 ms |
| Aug 29, 2026 | 107 ms |
| Sep 5, 2026 | 105 ms |
| Sep 12, 2026 | 106 ms |
| Sep 19, 2026 | 112 ms |
| Sep 26, 2026 | 120 ms |
| Oct 3, 2026 | 123 ms |
| Oct 10, 2026 | 126 ms |
| Oct 17, 2026 | 135 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
How it loaded on a phone
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
3,435 HTML elements
The page has 3,435 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Mobile performance score: 68
68/100Your mobile performance score is 68 (desktop: 85). Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
600 ms · 66 KiBAbout 66 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 600 ms faster on a phone.
Reduce unused CSS
300 ms · 90 KiBAbout 90 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
Render-blocking requests
300 ms1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 300 ms.
6 third-party services on the page
6 third-party services load with your homepage (Google Tag Manager, Google Optimize and Google Fonts and others), adding 545 KiB and 56 ms of main-thread time.
2 long tasks on the main thread
2 long tasks block the main thread while loading, the longest for 78 ms. During a long task the page ignores taps.
Improve image delivery
76 KiB2 images could be 76 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
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.
2 checks passed
Main-thread work: 0.6 s
A phone's processor spends 0.6 s on main-thread work while loading, 193 ms of it running JavaScript. That is comfortably low.
Server response: 11 ms
11 msYour server sent the HTML in 11 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.
Real-user TTFB: 1.9 s
1.9 sReal visitors wait 1.9 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 5.8 s
5.8 sYour largest element takes 5.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image. Most of its time is resource load delay (2.3 s).
First Contentful Paint: 3.6 s
3.6 sThe first text or image appears after 3.6 s on a phone. Good is under 1.8 s.
Real-user LCP: 2.7 s
2.7 sReal visitors wait 2.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.11
0.11For real visitors the layout shifts by 0.11 (75th percentile). Good is under 0.1.
Real-user FCP: 2.4 s
2.4 sReal visitors see the first content after 2.4 s (75th percentile). Good is under 1.8 s.
Speed Index: 4.9 s
4.9 sVisually, the page fills in at 4.9 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 5.8 s
5.8 sThe page becomes fully interactive after 5.8 s. Good is under 3.8 s.
Tap response (INP) got 18% slower for real visitors
+18%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 111 ms to 135 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
0%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.8 s to 2.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user INP: 146 ms
146 msReal visitors wait 146 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Cumulative Layout Shift: 0.035
0.035The layout barely moves while loading (CLS 0.035, good is under 0.1).
Total Blocking Time: 41 ms
41 msScripts block the page for only 41 ms while loading. Good is under 200 ms.
Images and page weight
1 image in older formats
1 image (43 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.3 g of CO₂ per visit
0.32 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.32 g of CO₂e: 38.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Page weight: 1.1 MB in 71 requests
1.1 MBYour homepage downloads 1.1 MB in 71 requests on a phone: other files 481 KiB (53), scripts 182 KiB (2) and fonts 172 KiB (7). That is a lean page.
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
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
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.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (2 elements)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.
10 tap targets too small
10 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.
2 checks passed
Every image has alt text
All 27 images in the HTML carry an alt attribute.
46 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 49 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 3 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 long (66 characters)
Your title is 66 characters, so Google will cut it off around 60: “Bering's | Shop Distinctive Hardware, Housewares, Gifts, and More.”.
7 H1 headlines
There are 7 <h1> headlines (“Holiday Gift Guide”, “Holiday Decor” and “Holiday Gifts”). One clear main headline is easier for people and search engines.
Structured data has 1 problem
Structured data found (BreadcrumbList, ImageObject, Organization and SiteNavigationElement) but with 1 problem, for example “WebSite: missing name”.
4 links with vague text
4 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
1,035 internal links, 24 external
The homepage links to 1,035 pages on berings.com and 24 external pages.
5 checks passed
Meta description: 139 characters
Your meta description is 139 characters: “Shop Berings.com and discover a curated selection of designer home goods, hardware and luxury items for your home. Fami…”.
Canonical URL set
The canonical URL is https://www.berings.com/.
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.
XML sitemap found
Your XML sitemap is reachable at https://www.berings.com/sitemap.xml.
AI search readiness
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.
llms.txt published
The site publishes https://www.berings.com/llms.txt (6 KiB, 59 links), a plain-text guide to the site for AI tools.
Other pages
15 pages without an H1
https://www.berings.com/shop/holiday, https://www.berings.com/shop/holiday/holiday-gourmet, https://www.berings.com/shop/holiday/holiday-decor, https://www.berings.com/shop/holiday/holiday-entertaining, https://www.berings.com/shop/holiday/holiday-gift-wrap and https://www.berings.com/shop/holiday/holiday-party-goods and 9 others 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 199 found) and read each the way a search engine does.
6 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.
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
25 small tap targets
25 of 50 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
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
Thin social proof
Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.
Only about 135 words
The homepage has only about 135 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
7 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Contact” and “Holiday Gift Guide SHOP NOW”.
16 calls to action
The homepage has 16 calls to action, for example “Contact”, “Learn More” and “Shop Men’s Accessories”.
8 short forms
8 short forms (3 fields at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager, Meta Pixel and Microsoft Clarity.
Direct contact links
Visitors can reach you directly: 4 phone links and 0 email links.
Opening hours shown
Your opening hours are on the homepage.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Google Ads and Google Tag Manager (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.
4 cookies set on arrival
4Opening the homepage sets 4 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.
7 other companies contacted
Loading the homepage contacts 7 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 berings.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
- E-commerce
- WooCommerce
- Analytics
- Google Tag Manager | Microsoft Clarity
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 29 issues on berings.com, including 14 speed issues, 4 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.