haskell.edu website review

Not measured in this review.

• Tap response (INP) got 21% slower for real visitors

  +21%

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

• Largest content (LCP) got 24% slower for real visitors

  +24%

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

• About 0.4 g of CO₂ per visit

  0.37 g

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

• 23 tap targets too small

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

  Elements (3)

• 5 text elements with low contrast

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

  Elements (3)

• 1 image without alt text

  1 image has no alt text, which hurts accessibility and image search.

  View sourceElements (1)

• All page content should be contained by landmarks (6 elements)

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

  Elements (3)

• No main landmark

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

  Elements (1)

• Page should contain a level-one heading (1 element)

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

  Elements (1)

• 1 link without text

  1 visible link has no text or label, so screen readers cannot say where it goes.

  Elements (2)

• Headings skip levels

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

  View sourceElements (1)

• No H1 headline

  There is no <h1>, so neither visitors nor Google get a clear main headline.

• 138 internal links, 27 external

  The homepage links to 138 pages on haskell.edu and 27 external pages.

• Organization data is thin (2 of 6 facts)

  Your Organization JSON-LD is missing logo, 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.

  View source

• No llms.txt

  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.

• 2 pages without a meta description

  /about and /commencement have no meta description, so Google writes the search snippet from whatever text it finds.

  Elements (2)

• 2 pages slow to respond

  /university-operations and /admissions/new-students took over 3 s to send their HTML from our server.

• 15 internal pages checked

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

• Scrolls sideways on phones

  On a 390 px-wide phone the page scrolls sideways, a sign that something is wider than the screen.

• 9 small tap targets

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

• 1 JavaScript error while loading

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

• No Content-Security-Policy

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

• HTTP/1.1 only

  The server only offers HTTP/1.1, so browsers open several connections and load files more slowly. Most hosts and CDNs turn on HTTP/2 with a setting.

• Short HSTS lifetime

  HSTS is set, but max-age is 7 days; one year is the recommended minimum.

• 1 link through redirect chains

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

• Deprecated X-XSS-Protection

  X-XSS-Protection is set to “1”; the header is deprecated and can introduce bugs. Use 0 or remove it.

• No security.txt

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

• No CAA record

  haskell.edu 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.

• No call to action on the first screen

  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 social proof

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

• Local business without LocalBusiness data

  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.

  View source

• Only about 244 words

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

• No opening hours

  The homepage shows no opening hours. If customers visit or call, show when.

• No map or directions link

  There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

• No risk reducer

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

• No DMARC policy

  haskell.edu has no DMARC record, so nothing tells receivers what to do with mail that fails SPF or DKIM. Gmail and Yahoo require DMARC from bulk senders.

• No DKIM key on the usual selectors

  We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

• Email authentication score: 40/100

  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.

• 3 trackers load before any consent

  3

  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.

• 5 cookies set on arrival

  5

  Opening the homepage sets 5 cookies (measured from a US location before any click).

• No consent tool detected

  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.

• 7 other companies contacted

  Loading the homepage contacts 7 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.