phantomshockey.com website review

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

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

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

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

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

8 third-party services load with your homepage (Vimeo, Facebook and Google Tag Manager and others), adding 9.5 MB and 763 ms of main-thread time.

Your mobile performance score is 53 (desktop: 73). Pages that score under 90 lose visitors before the first paint.

Vimeo costs a phone 215 ms of main-thread work and 6.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.

Facebook costs a phone 176 ms of main-thread work and 371 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 2,057 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

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

Adobe TypeKit costs a phone 0 ms of main-thread work and 624 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.

About 27 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.

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

Polyfills for old browsers add 20 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.

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

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

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

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

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

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

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

Your homepage downloads 17.5 MB in 149 requests on a phone: images 6.9 MB (70), other files 5.8 MB (30) and scripts 2.1 MB (35). Under 2 MB keeps phones on slow connections fast.

25 images are downloaded at several times the size a phone draws them, for example P1011_0449-scaled-aspect-ratio-4-3-1536x1151.jpg at 1,536 px wide, shown at 349 px. Resized copies would save about 2.1 MB.

40 images (5.3 MB) 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.

13 images further down the page (1.8 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

198 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

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

1 element hidden from screen readers can still receive keyboard focus.

1 image has no alt text, which hurts accessibility and image search.

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

2 form fields have no label, so screen readers announce an empty box and autofill guesses.

Elements with visible text labels do not have matching accessible names. (12 elements).

Your title is only 22 characters: “Lehigh Valley Phantoms”. Between 30 and 65 characters leaves room to say what you do and for whom.

There are 6 <h1> headlines (“Phantoms Weekly”, “Bump AHL Player of Week” and “Bump and Knuble to Flyers”). One clear main headline is easier for people and search engines.

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

The homepage links to 108 pages on phantomshockey.com and 90 external pages.

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

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

5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

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

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

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.

The homepage shows no opening hours. If customers visit or call, show when.

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,196 words of visible text.

The page uses urgency cues (a countdown or limited-time wording).

Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager and Meta Pixel (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 6 cookies, 2 of them by other companies (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 20 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.