wis.edu website review

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

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

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

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

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

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, amais.com and Vimeo and others), adding 15.7 MB and 1.2 s of main-thread time.

amais.com costs a phone 406 ms of main-thread work and 11.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.

Vimeo costs a phone 274 ms of main-thread work and 3.5 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.

Google Tag Manager costs a phone 490 ms of main-thread work and 510 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,681 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

19 KiB could be saved by minifying CSS.

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

6 KiB could be saved by minifying JavaScript.

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 6.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

Your largest element takes 23.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “WASHINGTON INTERNATIONAL SCHOOL”. Most of its time is element render delay (9.7 s).

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

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

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

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

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

9 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' tap response (inp) went from 113 ms to 127 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 15.9 MB in 220 requests on a phone: images 11.4 MB (126), other files 2.2 MB (36) and scripts 1.6 MB (26). Under 2 MB keeps phones on slow connections fast.

5 images weigh 2.8 MB together. On a phone connection a single image that size takes seconds.

11 images are downloaded at several times the size a phone draws them, for example Homepage_blog_pic-4761-optimized.webp at 2,560 px wide, shown at 350 px. Resized copies would save about 2.4 MB.

38 images further down the page (6.2 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

1 image (350 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 4.52 g of CO₂e: 542.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 element hidden from screen readers can still receive keyboard focus.

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

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

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

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

Your title is only 10 characters: “Home | WIS”. 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.

There are 2 <h1> headlines (“Home | WIS” and “Home”). One clear main headline is easier for people and search engines.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 289 pages on wis.edu and 13 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.wis.edu/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://www.wis.edu/about-wis and https://www.wis.edu/mission-values all use the title “About | Who We Are | WIS”, and 3 other titles repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.wis.edu/technology-at-wis has no meta description, so Google writes the search snippet from whatever text it finds.

https://www.wis.edu/calendars, https://www.wis.edu/about-wis, https://www.wis.edu/mission-values, https://www.wis.edu/meet-us, https://www.wis.edu/wis-leadership and https://www.wis.edu/board-governance and 3 others 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.wis.edu/about-wis, whose canonical is https://www.wis.edu/mission-values. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.wis.edu/diversity, https://www.wis.edu/idi-community-spotlights, https://www.wis.edu/meet-us and https://www.wis.edu/wis-leadership took over 3 s to send their HTML from our server.

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

2 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 (“Unload event listeners are deprecated and will be removed.”).

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

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

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: 1 trust badge. 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 form on the homepage, so every lead has to click through to another page first.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (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 6 cookies, 2 of them by other companies (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 20 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.