fernbaughs.com website review

7 files are served with short cache lifetimes, so returning visitors download them again (309 KiB).

Your mobile performance score is 85. Pages that score under 90 lose visitors before the first paint.

8 third-party services load with your homepage (Google Tag Manager, podium.com and Accessibe Accessibility Overlay and others), adding 1.3 MB and 584 ms of main-thread time.

3 files block the first paint until they finish downloading. Deferring or inlining them could save about 650 ms.

About 529 KiB of JavaScript is downloaded but never used on this page.

Google Tag Manager costs a phone 262 ms of main-thread work and 470 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.

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

podium.com costs a phone 158 ms of main-thread work and 494 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.

The page has 1,549 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

5 long tasks block the main thread while loading, the longest for 180 ms. During a long task the page ignores taps.

About 26 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

1 image could be 5 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

3 KiB JavaScript is shipped twice across bundles.

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

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

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

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

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.5 s to 1.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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.

Your homepage downloads 2.8 MB in 212 requests on a phone: scripts 1.1 MB (39), other files 989 KiB (144) and images 388 KiB (12). Under 2 MB keeps phones on slow connections fast.

4 images (349 KiB) are 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.

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

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

1 frame has no title, so screen-reader users cannot tell what it contains.

All page content should be contained by landmarks: 25 elements on the page fail this check, rated moderate by axe-core.

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

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

Headings skip levels (h1 → h6), which makes the page harder to scan with a screen reader.

Your title is 76 characters, so Google will cut it off around 60: “Jewelry Store in Plymouth, IN - Jewelry Store Near Me – Fernbaugh's Jewelers”.

Your meta description is 228 characters; Google truncates after about 160, so the end of your pitch is cut.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

The homepage links to 145 pages on fernbaughs.com and 12 external pages.

Your Organization JSON-LD is missing logo, description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

/collections/new-arrivals, /collections/in-stock-engagement-rings, /collections/oval-engagement-rings, /collections/gabriel-co-engagement-rings and /collections/sallyk-wedding-bands have no meta description, so Google writes the search snippet from whatever text it finds.

We fetched 15 pages linked from your homepage (of 70 found) and read each the way a search engine does.

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

HSTS is set, but max-age is 91 days; one year is the recommended minimum.

3 links go through two or more redirects, for example https://fernbaughsjewelers.com/customer_authentication/redirect?locale=en&region_country=US.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

fernbaughsjewelers.com is registered until Jan 2027. Make sure auto-renew is on and the card on file is current.

fernbaughsjewelers.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

fernbaughsjewelers.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 1,563 words of visible text.

fernbaughs.com has no DMARC record, so nothing tells receivers what to do with mail that fails SPF or DKIM. Gmail and Yahoo require DMARC from bulk senders.

We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Ads and 1 more (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.

Opening the homepage sets 11 cookies (measured from a US location before any click).

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.

Loading the homepage contacts 23 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.