dcprep.org website review

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

About 972 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.4 s faster on a phone.

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

About 235 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 2.1 s faster on a phone.

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

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

8 third-party services load with your homepage (Google Tag Manager, Facebook and weglot.com and others), adding 1.2 MB and 694 ms of main-thread time.

Google Tag Manager costs a phone 396 ms of main-thread work and 441 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 2.9 s on main-thread work while loading, 1.5 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 216 ms. During a long task the page ignores taps.

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

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

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 wait 1.9 s for your server to start answering (75th percentile). Good is under 800 ms.

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

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

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

Real visitors wait 3.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

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

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

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

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

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

Your homepage downloads 11.2 MB in 97 requests on a phone: images 4.8 MB (55), media 4.1 MB (6) and scripts 1.7 MB (11). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example dodrid125nx6but3mlfy.png at 305 px wide, shown at 56 px. Resized copies would save about 78 KiB.

1 image (112 KiB) is 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.

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

ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

ARIA role should be appropriate for the element: 2 elements on the page fail this check, rated minor by axe-core.

Your title is only 14 characters: “Home - DC Prep”. 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 14 characters: “Home - DC Prep”. 70 to 160 characters is enough to sell the click.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

1 link has no real href, so search engines can't follow it.

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

The homepage links to 92 pages on dcprep.org and 5 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 /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.

/about/board-of-directors is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

/current-families, /calendar, /academics/prepnext, /about/careers and /enrollment/our-campuses took over 3 s to send their HTML from our server.

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

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

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

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

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

Large scripts ship without source maps.

1 link go through two or more redirects, for example http://facebook.com/dcprep.

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.

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

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

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