Website review, no card needed

ibgoodman.com logo

ibgoodman.com website review

Visit site (opens in a new tab)Reviewed 20 November 202639 issues · 59 checks

This review found 39 issues worth fixing on ibgoodman.com, 16 of them high impact, across 59 checks. The most urgent: avoid multiple page redirects. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Full-page screenshot of ibgoodman.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. ibgoodman.com at 3.7 s3.7 s
  2. ibgoodman.com at 7.4 s7.4 s
  3. ibgoodman.com at 11.1 s11.1 s
  4. ibgoodman.com at 14.7 s14.7 s
  5. ibgoodman.com at 18.4 s18.4 s
  6. ibgoodman.com at 22.1 s22.1 s
  7. ibgoodman.com at 25.8 s25.8 s
  8. ibgoodman.com at 29.5 s29.5 s

Speed

11 to fix4
  • Avoid multiple page redirects

    34.1 s

    The page goes through 1 redirect before it starts loading, costing about 34.1 s. Link and advertise the final URL directly.

  • Reduce unused JavaScript

    24.1 s · 3.3 MB

    About 3.3 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 24.1 s faster on a phone.

  • Main-thread work: 12.3 s

    A phone's processor spends 12.3 s on main-thread work while loading, 7.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • Mobile performance score: 4

    4/100

    Your mobile performance score is 4. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, zoom.us and Google CDN and others), adding 11.9 MB and 523 ms of main-thread time.

  • 19 long tasks on the main thread

    19 long tasks block the main thread while loading, the longest for 1.6 s. During a long task the page ignores taps.

  • jewelers.services adds 4 ms

    4 ms

    jewelers.services costs a phone 4 ms of main-thread work and 9.4 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.

  • zoom.us adds 127 ms

    127 ms

    zoom.us costs a phone 127 ms of main-thread work and 428 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.

  • Google CDN adds 106 ms

    106 ms

    Google CDN costs a phone 106 ms of main-thread work and 352 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.

  • Google Maps adds 85 ms

    85 ms

    Google Maps costs a phone 85 ms of main-thread work and 329 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.

  • qgold.com adds 0 ms

    0 ms

    qgold.com costs a phone 0 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.

  • Minify JavaScript

    150 ms · 124 KiB

    124 KiB could be saved by minifying JavaScript.

  • Font display

    150 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 150 ms).

  • 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: 1 ms

    1 ms

    Your server sent the HTML in 1 ms, well inside Google's 600 ms guideline.

Core Web Vitals

7 to fix5
  • First Contentful Paint: 10.2 s

    10.2 s

    The first text or image appears after 10.2 s on a phone. Good is under 1.8 s.

  • Largest Contentful Paint: 35.7 s

    35.7 s

    Your largest element takes 35.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • Speed Index: 28.4 s

    28.4 s

    Visually, the page fills in at 28.4 s (Speed Index). Good is under 3.4 s.

  • Time to Interactive: 50.3 s

    50.3 s

    The page becomes fully interactive after 50.3 s. Good is under 3.8 s.

  • Total Blocking Time: 2.9 s

    2.9 s

    Scripts block taps and scrolling for 2.9 s in total while the page loads. Good is under 200 ms.

  • Cumulative Layout Shift: 0.594

    0.594

    The layout shifts by 0.594 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • 6 images without width and height

    6 images have no width and height attributes, so the layout jumps as each one loads.

  • 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.

Images and page weight

1 to fix33
  • Page weight: 16.4 MB in 176 requests

    16.4 MB

    Your homepage downloads 16.4 MB in 176 requests on a phone: images 10.4 MB (56), scripts 5.5 MB (40) and stylesheets 250 KiB (8). Under 2 MB keeps phones on slow connections fast.

  • About 4.6 g of CO₂ per visit

    4.64 g

    By the Sustainable Web Design model, a visit to your homepage emits about 4.64 g of CO₂e: 556.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Accessibility

4 to fix76
  • 4 buttons without a name

    4 buttons have no accessible name, so screen readers announce just “button”.

  • 7 tap targets too small

    7 tap targets are too small or too close together to hit reliably with a finger.

  • 2 links without text

    2 visible links have no text or label, so screen readers cannot say where they go.

  • ARIA progressbar elements do not have accessible names.

    ARIA progressbar elements do not have accessible names. (1 element).

SEO

7 to fixGoogle 6774
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • No XML sitemap

    No XML sitemap at https://ibgoodman.com/sitemap.xml, so Google discovers your pages only by following links.

  • No robots.txt

    There is no robots.txt at ibgoodman.com/robots.txt, the first file search crawlers ask for.

  • Only 0 internal links

    The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.

  • 9 links crawlers can't follow

    9 links have no real href, so search engines can't follow them.

  • 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.

4 checks passed
  • Meta description: 155 characters

    Your meta description is 155 characters: “Traditional craftsmanship and superior materials are used to create lasting Men's jewelry. We specialize in Masonic Rin…”.

  • Title: 62 characters

    Your title is a healthy 62 characters: “Manufacturer of Fine Men's Jewelry and Accessories - IBGoodman”.

  • Canonical URL set

    The canonical URL is http://ibgoodman.com/.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

AI search readiness

1 to fix83
  • 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://ibgoodman.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.

1 checks passed
  • AI answer engines may read the site

    There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.

Best practices

2 to fixGoogle 6987
  • 3 small tap targets

    3 of 6 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “ERROR TypeError: Cannot read properties of null (reading 'findIndex')”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Mixed content”).

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix33
  • 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 calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

  • 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 7 words

    The homepage has only about 7 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.

1 checks passed
  • Analytics in place

    Analytics detected: Google Analytics.

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads 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.

  • 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.

  • 9 other companies contacted

    Loading the homepage contacts 9 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 ibgoodman.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 Analytics
Hosting
Quality Gold, Inc.

Company

Headquarters
Newport

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 39 issues on ibgoodman.com, including 18 speed issues, 7 SEO issues and 5 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25