oppd.com website review

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

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

Google Tag Manager costs a phone 1.8 s of main-thread work and 1.0 MB 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 15. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

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

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

About 695 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 600 ms faster on a phone.

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

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

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

31 KiB could be saved by minifying JavaScript.

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

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

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

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

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

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

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

The layout shifts by 0.431 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

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

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-31, real Chrome visitors' largest content (lcp) went from 1.6 s to 1.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 6.2 MB in 126 requests on a phone: images 4.2 MB (33), scripts 1.8 MB (46) and HTML 142 KiB (4). Under 2 MB keeps phones on slow connections fast.

4 images weigh 2.7 MB together. On a phone connection a single image that size takes seconds.

10 images (3.5 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.

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

1 element use ARIA attributes their role does not allow, which confuses screen readers.

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

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

1 link inside paragraphs relies on colour alone to stand out.

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

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

Your title is only 13 characters: “OPPD Homepage”. 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.

Your meta description is only 34 characters: “OPPD - Omaha Public Power District”. 70 to 160 characters is enough to sell the click.

There are 3 <h1> headlines (“DOWNLOADMYOPPD APP”, “DOWNLOAD MYOPPD APP” and “MyOPPD”). One clear main headline is easier for people and search engines.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

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://oppd.com/sitemap.xml, so Google discovers your pages only by following links.

There is no robots.txt at oppd.com/robots.txt, the first file search crawlers ask for.

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

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

The homepage links to 376 pages on oppd.com and 44 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://oppd.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.

https://oppd.com/contact and https://oppd.com/residential/customer-service/contacts-office-information all use the title “Contact Information”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://oppd.com/about/careers, https://oppd.com/espanol, https://oppd.com/contact, https://oppd.com/residential, https://oppd.com/residential/customer-service and https://oppd.com/residential/customer-service/manage-properties and 9 others use the same meta description. A description written for each page earns more clicks.

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

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

2 errors were logged to the browser console while the page loaded, for example “Failed to find a valid digest in the 'integrity' attribute for resource 'https://code.jquery.com/ui/1.13.2/jquery-ui.mi…”.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

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

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

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 167 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, Meta Pixel and Xandr (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 18 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 26 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.