2ndswing.com website review

91 files are served with short cache lifetimes, so returning visitors download them again (6.5 MB).

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

21 images could be 7.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.6 s faster on a phone.

704 KiB could be saved by minifying JavaScript.

22 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.8 s.

About 248 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.9 s faster on a phone.

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

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

8 third-party services load with your homepage (Google Tag Manager, Google Maps and Facebook and others), adding 4.3 MB and 1.6 s of main-thread time.

Google Tag Manager costs a phone 561 ms of main-thread work and 733 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 costs a phone 341 ms of main-thread work and 1,015 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.

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

9 KiB could be saved by minifying CSS.

Facebook costs a phone 222 ms of main-thread work and 308 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.

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

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

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

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

Polyfills for old browsers add 46 KiB JavaScript that modern phones do not need.

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.

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.

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

Your largest element takes 59.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Swing Days: limited-time deals and price drops on select cl…”.

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

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

Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' tap response (inp) went from 104 ms to 130 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Real visitors wait 968 ms for your server to start answering (75th percentile). Good is under 800 ms.

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

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

Your homepage downloads 25.2 MB in 273 requests on a phone: media 9.5 MB (1), images 8.4 MB (43) and scripts 5.9 MB (98). Under 2 MB keeps phones on slow connections fast.

2S_HDWGH_HomeDsktpBanner_2000x550_1.png weighs 714 KiB. On a phone connection a single image that size takes seconds.

2nd-Swing-Golf-Store.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

4 images (182 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 7.15 g of CO₂e: 858.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.

Form elements should have a visible label: 1 element on the page fails this check, rated serious by axe-core.

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 on the page fail this check, rated moderate by axe-core.

1 visible link has no text or label, so screen readers cannot say where it goes.

Elements with visible text labels do not have matching accessible names. (1 element).

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is only 14 characters: “2nd Swing Golf”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

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

3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

1 link has no real href, so search engines can't follow it.

Open Graph is missing og:description, so shared links fall back to guesses.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 105 pages on 2ndswing.com and 7 external pages.

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.

There is no /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.

/golf-club-selector-tools/fitting-surveys has no <h1> headline, so visitors and search engines get no clear main topic.

/golf-clubs took over 3 s to send its HTML from our server.

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

2 images failed to load on a phone, for example https://lantern.roeye.com/track.php?fingerprint=3839f495-d801-4ae1-9ecb-2db2b3a8bea4&referrer=&landingpage=https%3A%2F%2Fwww.2ndswing.com%2F&useragent=Mozilla%2F5.0%20(iPhone%3B%20CPU%20iPhone%20OS%20.

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

5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

Large scripts ship without source maps.

No Content-Security-Policy header, the main browser-side defence against injected scripts.

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

2 links go through two or more redirects, for example https://www.2ndswing.com/customer/clubhouse.

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.

2ndswing.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.

2ndswing.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 map but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

The homepage carries about 380 words of visible text.

2ndswing.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.

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, Hotjar and Meta Pixel and 4 mores (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 40 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 54 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.