compudopt.org website review

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

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

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

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

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

10 files are served with short cache lifetimes, so returning visitors download them again (460 KiB).

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

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

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

About 312 KiB of JavaScript is downloaded but never used on this page.

Google Fonts costs a phone 0 ms of main-thread work and 388 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 12 KiB JavaScript that modern phones do not need.

Desktop scores 64 but mobile only 17. A gap that wide usually means heavy scripts and images that hit phones hardest.

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.

2 KiB could be saved by minifying JavaScript.

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.

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

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

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

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

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

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

Real visitors wait 243 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

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

Your homepage downloads 18.0 MB in 139 requests on a phone: images 12.1 MB (54), media 4.4 MB (1) and scripts 981 KiB (29). Under 2 MB keeps phones on slow connections fast.

8 images weigh 7.6 MB together. On a phone connection a single image that size takes seconds.

14 images (8.2 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.

CompudoptNewportNightOut-16-edit-2000px-768x768.png 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 further down the page (801 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

7 images are downloaded at several times the size a phone draws them, for example United-Way-of-Dallas-Logo-768x495.jpeg at 390 px wide, shown at 121 px. Resized copies would save about 150 KiB.

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

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

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

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

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

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

Your title is 74 characters, so Google will cut it off around 60: “Tech Access: Free Computers, Low-Cost Internet, Tech Education | Compudopt”.

There are 4 <h1> headlines (“Empowering communities with digital access.”, “Get Connected with low-cost 5G internet” and “Transforming communities through tech education”). One clear main headline is easier for people and search engines.

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

The homepage links to 86 pages on compudopt.org and 8 external pages.

Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

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.

/programs/compudopt-connect-low-cost-internet and /compudopt-connect-low-cost-internet all use the title “Compudopt Connect Low Cost Internet | Compudopt”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

/tech-support, /ways-to-give and /ways-to-give/donate have no meta description, so Google writes the search snippet from whatever text it finds.

/programs/compudopt-connect-low-cost-internet and /compudopt-connect-low-cost-internet 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 /programs/compudopt-connect-low-cost-internet, whose canonical is /compudopt-connect-low-cost-internet. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

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

7 of 14 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 “Unexpected token '<'”.

No Strict-Transport-Security header, so browsers may still try plain http first on a return visit.

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

Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

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.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

compudopt.org 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.

compudopt.org'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.

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.

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

DMARC is set to p=none, so mail pretending to be compudopt.org is still delivered. Add a report address, check the reports, then move to quarantine.

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, LinkedIn Insight 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 8 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 21 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.