optimum.net website review

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

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

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

New Relic costs a phone 1.0 s of main-thread work and 64 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

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

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

8 third-party services load with your homepage (New Relic, ccaiplatform.com and Google Tag Manager and others), adding 2.7 MB and 2.8 s of main-thread time.

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

106 KiB could be saved by minifying JavaScript.

ccaiplatform.com costs a phone 468 ms of main-thread work and 1.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.

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

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

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

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

78 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 300 ms faster on a phone.

Facebook costs a phone 307 ms of main-thread work and 275 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 150 ms).

11 KiB could be saved by minifying CSS.

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.

Real visitors see the first content after 3.9 s (75th percentile). Good is under 1.8 s.

Your largest element takes 31.4 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 34.9 s. Good is under 3.8 s.

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

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

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

Real visitors wait 3.9 s for the largest content to appear (75th percentile). Good is under 2.5 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-03, real Chrome visitors' tap response (inp) went from 153 ms to 160 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 4.2 s to 4.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 5.6 MB in 185 requests on a phone: scripts 3.9 MB (46), images 1.2 MB (65) and fonts 293 KiB (6). Under 2 MB keeps phones on slow connections fast.

6 images (878 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.

1 image further down the page (76 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

By the Sustainable Web Design model, a visit to your homepage emits about 1.58 g of CO₂e: 189.1 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”.

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

<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

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

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

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

The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

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

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

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

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

There are 5 <h1> headlines (“How can we help you?”, “I need help with...” and “My services”). One clear main headline is easier for people and search engines.

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

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

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

The homepage links to 270 pages on optimum.net and 93 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 https://www.optimum.net/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.

Your homepage links to https://www.optimum.net/%7B%7BCommonHeaderCtrl.helloMessage.link%7D%7D, which answers with an error. Visitors hit a dead end and search engines drop it.

https://www.optimum.net/internet is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://www.optimum.net/internet/manage-devices, https://www.optimum.net/pay-bill, https://www.optimum.net/pay-bill/combined-billsummary and https://www.optimum.net/pay-bill/my-bill all use the title “Optimum | Callback”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.optimum.net/internet has no meta description, so Google writes the search snippet from whatever text it finds.

https://www.optimum.net/internet/manage-devices, https://www.optimum.net/pay-bill, https://www.optimum.net/pay-bill/payin-person, https://www.optimum.net/FAQ, https://www.optimum.net/pay-bill/combined-billsummary and https://www.optimum.net/pay-bill/my-bill and 2 others use the same meta description. A description written for each page earns more clicks.

https://www.optimum.net/FAQ and https://www.optimum.net/support/phone have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.optimum.net/internet/manage-devices, https://www.optimum.net/pay-bill, https://www.optimum.net/pay-bill/combined-billsummary, https://www.optimum.net/pay-bill/my-bill and https://www.optimum.net/support/user-guides took over 3 s to send their HTML from our server.

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

No viewport meta tag, so phones render the desktop layout zoomed out.

1 image failed to load on a phone, for example https://archetype-military-times-prod.web.arc-cdn.net/resizer/v2/cDgi-Ha6GGvclUrfOkEU2T82MQc=https://www.optimum.net/www.cheddar.com/resizer/t-n-LRNoU61VqwBKBGnOubbpteQ=/www.cheddar.com/resizer//84quPlCktdOxA9x9hIpPBkhzHKk=.

6 of 21 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 (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).

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 404 (Not Found)”.

No character set is declared, so some characters can render as gibberish.

1 image is served at too low a resolution for sharp phone screens.

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

Large scripts ship without source maps.

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

The homepage has only about 181 words of visible text; thin pages give Google and first-time buyers little to go on.

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

Before a visitor clicks anything, the page loads Google Ads, 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 26 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 31 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.