Website review, no card needed
govbergwatches.com website review
Visit site (opens in a new tab)Reviewed 25 October 202627 issues · 74 checks
This review found 27 issues worth fixing on govbergwatches.com, 9 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
73CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 2.3 s |
| May 9, 2026 | 2.3 s |
| May 16, 2026 | 2.3 s |
| May 23, 2026 | 2.3 s |
| May 30, 2026 | 2.2 s |
| Jun 6, 2026 | 2.2 s |
| Jun 13, 2026 | 2.3 s |
| Jun 20, 2026 | 2.3 s |
| Jun 27, 2026 | 2.2 s |
| Jul 4, 2026 | 2.2 s |
| Jul 11, 2026 | 2.2 s |
| Jul 18, 2026 | 2.1 s |
| Jul 25, 2026 | 2.1 s |
| Aug 1, 2026 | 2.1 s |
| Aug 8, 2026 | 2.1 s |
| Aug 15, 2026 | 2.1 s |
| Aug 22, 2026 | 2.1 s |
| Aug 29, 2026 | 2.1 s |
| Sep 5, 2026 | 2.1 s |
| Sep 12, 2026 | 2.1 s |
| Sep 19, 2026 | 2.1 s |
| Sep 26, 2026 | 2.1 s |
| Oct 3, 2026 | 2.2 s |
| Oct 10, 2026 | 2.2 s |
| Oct 17, 2026 | 2.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 162 ms |
| May 9, 2026 | 162 ms |
| May 16, 2026 | 163 ms |
| May 23, 2026 | 163 ms |
| May 30, 2026 | 166 ms |
| Jun 6, 2026 | 171 ms |
| Jun 13, 2026 | 174 ms |
| Jun 20, 2026 | 174 ms |
| Jun 27, 2026 | 171 ms |
| Jul 4, 2026 | 170 ms |
| Jul 11, 2026 | 166 ms |
| Jul 18, 2026 | 168 ms |
| Jul 25, 2026 | 170 ms |
| Aug 1, 2026 | 169 ms |
| Aug 8, 2026 | 175 ms |
| Aug 15, 2026 | 177 ms |
| Aug 22, 2026 | 179 ms |
| Aug 29, 2026 | 180 ms |
| Sep 5, 2026 | 177 ms |
| Sep 12, 2026 | 179 ms |
| Sep 19, 2026 | 181 ms |
| Sep 26, 2026 | 187 ms |
| Oct 3, 2026 | 191 ms |
| Oct 10, 2026 | 192 ms |
| Oct 17, 2026 | 193 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.2 s
1.6 s
2.0 s
2.4 s
2.8 s
3.2 s
Speed
Reduce unused JavaScript
1.2 s · 250 KiBAbout 250 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: 62
62/100Your mobile performance score is 62 (desktop: 96). Pages that score under 90 lose visitors before the first paint.
4 third-party services on the page
4 third-party services load with your homepage (Optanon, userway.org and Cloudflare and others), adding 2.6 MB and 163 ms of main-thread time.
Render-blocking requests
300 ms2 files block the first paint until they finish downloading. Deferring or inlining them could save about 300 ms.
imgix adds 0 ms
0 msimgix costs a phone 0 ms of main-thread work and 2.3 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.
Legacy JavaScript
250 ms · 37 KiBPolyfills for old browsers add 37 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
200 ms · 75 KiB9 files are served with short cache lifetimes, so returning visitors download them again (75 KiB).
Improve image delivery
150 ms · 95 KiB5 images could be 95 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.
3 long tasks on the main thread
3 long tasks block the main thread while loading, the longest for 77 ms. During a long task the page ignores taps.
Reduce unused CSS
21 KiBAbout 21 KiB of CSS is downloaded but never applied on this page.
Phones get a much slower page than desktops
Desktop scores 96 but mobile only 62. A gap that wide usually means heavy scripts and images that hit phones hardest.
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.
Duplicated JavaScript
4 KiB4 KiB JavaScript is shipped twice across bundles.
2 checks passed
Main-thread work: 1.3 s
A phone's processor spends 1.3 s on main-thread work while loading, 867 ms of it running JavaScript. That is comfortably low.
Server response: 36 ms
36 msYour server sent the HTML in 36 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.
Largest Contentful Paint: 8.7 s
8.7 sYour largest element takes 8.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Rolex”.
First Contentful Paint: 3.8 s
3.8 sThe first text or image appears after 3.8 s on a phone. Good is under 1.8 s.
Speed Index: 6.7 s
6.7 sVisually, the page fills in at 6.7 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 8.8 s
8.8 sThe page becomes fully interactive after 8.8 s. Good is under 3.8 s.
Real-user INP: 238 ms
238 msReal visitors wait 238 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.22
0.22For real visitors the layout shifts by 0.22 (75th percentile). Good is under 0.1.
Real-user TTFB: 1.0 s
1.0 sReal visitors wait 1.0 s for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 19% slower for real visitors
+19%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 162 ms to 193 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-6%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.3 s to 2.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user LCP: 1.5 s
1.5 sReal visitors wait 1.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 1.5 s
1.5 sReal visitors see the first content after 1.5 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: 54 ms
54 msScripts block the page for only 54 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 3.2 MB in 71 requests
3.2 MBYour homepage downloads 3.2 MB in 71 requests on a phone: media 1.9 MB (4), scripts 670 KiB (26) and fonts 253 KiB (5). Under 2 MB keeps phones on slow connections fast.
About 0.9 g of CO₂ per visit
0.89 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.89 g of CO₂e: 107.3 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
All page content should be contained by landmarks (2 elements)
All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.
2 checks passed
Every image has alt text
All 13 images in the HTML carry an alt attribute.
45 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 46 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 1 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
197 internal links, 8 external
The homepage links to 197 pages on govbergwatches.com and 8 external pages.
8 checks passed
Meta description: 156 characters
Your meta description is 156 characters: “Shop luxury watches, fine jewelry, and authenticated pre-owned handbags at The 1916 Company. Discover curated designer …”.
One H1 headline
Your main headline reads: “Luxury Watches, Jewelry & Pre-Owned Handbags | The 1916 Company”.
Title: 59 characters
Your title is a healthy 59 characters: “Luxury Watches, Jewelry & Pre-Owned Handbags | 1916 Company”.
Canonical URL set
The canonical URL is https://www.the1916company.com/.
Structured data in place
Structured data found: BreadcrumbList.
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://www.the1916company.com/sitemap.xml.
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.
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.
llms.txt published
The site publishes https://www.the1916company.com/llms.txt (8 KiB, 76 links), a plain-text guide to the site for AI tools.
Other pages
2 linked pages hidden from search
https://www.the1916company.com/wishlist and https://www.the1916company.com/bag are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.
2 pages share a title
https://www.the1916company.com/contact-us and https://www.the1916company.com/bag all use the title “Luxury Watches and Jewelry | Trade, Sell, Buy Luxury Watches and Jewe…”. Search engines can't tell which page to show for a search, so each competes with the others.
2 pages share a meta description
https://www.the1916company.com/bag and https://www.the1916company.com/about-us/110-anniversary use the same meta description. A description written for each page earns more clicks.
11 pages without an H1
https://www.the1916company.com/locations, https://www.the1916company.com/bag, https://www.the1916company.com/rolex, https://www.the1916company.com/rolex/rolex-collection, https://www.the1916company.com/rolex/new-watches and https://www.the1916company.com/rolex/1908 and 5 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 148 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.
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.
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://www.the1916company.com/.
6 small tap targets
6 of 23 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 social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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.
Only about 119 words
The homepage has only about 119 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
2 checks passed
12 calls to action
The homepage has 12 calls to action, for example “Contact Us”, “Shop All” and “Shop All Pre-Owned Jewelry”.
Analytics in place
Analytics detected: Google Tag Manager and Cloudflare Web Analytics.
Privacy and tracking
16 cookies set on arrival
16Opening the homepage sets 16 cookies (measured from a US location before any click).
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.
2 checks passed
Consent tool: OneTrust
A consent management tool (OneTrust) loads with the page.
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 govbergwatches.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Analytics
- Google Tag Manager
- Hosting
- AWS
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 27 issues on govbergwatches.com, including 13 speed issues and 4 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.