wfmz.com website review

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

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

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

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

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

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

8 third-party services load with your homepage (spoteam.com, Google Tag Manager and Rubicon Project and others), adding 7.0 MB and 3.2 s of main-thread time.

spoteam.com costs a phone 835 ms of main-thread work and 367 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 Tag Manager costs a phone 517 ms of main-thread work and 878 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.

Rubicon Project costs a phone 488 ms of main-thread work and 105 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.

Polyfills for old browsers add 33 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 400 ms faster on a phone.

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

townnews.com costs a phone 288 ms of main-thread work and 599 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.

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

4 images could be 31 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 100 ms faster on a phone.

70 KiB could be saved by minifying JavaScript.

About 39 KiB of CSS is downloaded but never applied on this page.

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 10.4 s on a phone. Good is under 1.8 s.

Your largest element takes 24.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “33-year-old Hunterdon County motorcyclist dead after accide…”.

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

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

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

For real visitors the layout shifts by 0.18 (75th percentile). Good is under 0.1.

2 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-03, real Chrome visitors' tap response (inp) went from 231 ms to 207 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 15.8 MB in 1,141 requests on a phone: media 7.3 MB (20), scripts 5.4 MB (125) and images 1.5 MB (332). Under 2 MB keeps phones on slow connections fast.

6aac3bd90dc7f.image.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).

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

1 button has no accessible name, so screen readers announce just “button”.

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

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

2 frames have no title, so screen-reader users cannot tell what they contain.

4 images have no alt text, which hurts accessibility and image search.

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

Elements marked as presentational should be consistently ignored: 34 elements on the page fail this check, rated minor by axe-core.

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

Headings skip levels (h2 → h4, h3 → h5 and h1 → h3), which makes the page harder to scan with a screen reader.

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

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

Structured data found (Organization) but with 5 problems, for example “Organization: sameAs is not an absolute URL ("[email protected]")”.

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

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 374 pages on wfmz.com and 26 external pages.

Your robots.txt shuts out ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User) and Perplexity (PerplexityBot). These fetch pages to answer people's questions and cite the source, so your site can't be quoted or linked in those answers.

There is no https://www.wfmz.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.

robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers.

https://www.wfmz.com/apps and https://www.wfmz.com/station/apps all use the title “Mobile and Free Apps - WFMZ-TV 69News | wfmz.com”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.wfmz.com/news/election, https://www.wfmz.com/news/area/lehighvalley/lehigh-county, https://www.wfmz.com/news/area/lehighvalley/lehigh-county/allentown-area, https://www.wfmz.com/news/area/lehighvalley/lehigh-county/bethlehem-area, https://www.wfmz.com/news/area/lehighvalley/lehigh-county/northern-lehigh-county and https://www.wfmz.com/news/area/lehighvalley/lehigh-county/southern-lehigh-county and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.wfmz.com/apps and https://www.wfmz.com/station/apps use the same meta description. A description written for each page earns more clicks.

Your homepage links to 3 pages by a URL that isn't their canonical one, for example https://www.wfmz.com/bigticket, whose canonical is https://www.wfmz.com/sports/bigticket. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.wfmz.com/apps, https://www.wfmz.com/streaming, https://www.wfmz.com/news, https://www.wfmz.com/station/apps, https://www.wfmz.com/news/election and https://www.wfmz.com/news/area/lehighvalley and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

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

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

4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 403 ()”.

8 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

3 images are served at too low a resolution for sharp phone screens.

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

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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.

Social proof on the homepage: 65 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

Before a visitor clicks anything, the page loads Amazon Ads, Comscore, Criteo, Google Ads and Google Analytics and 2 mores (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

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

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