hsf.net website review

48 images could be 11.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

6 third-party services load with your homepage (Hotjar, Google Tag Manager and YouTube and others), adding 12.2 MB and 483 ms of main-thread time.

About 1.7 MB of JavaScript is downloaded but never used on this page.

Amazon Web Services costs a phone 0 ms of main-thread work and 11.8 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.

Your mobile performance score is 70. Pages that score under 90 lose visitors before the first paint.

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

Hotjar costs a phone 325 ms of main-thread work and 65 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.

About 260 KiB of CSS is downloaded but never applied on this page.

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

The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

9 KiB JavaScript is shipped twice across bundles.

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

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

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

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

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

Your largest element takes 2.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “HSF empowers students and parents with the knowledge and re…”.

Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 162 ms to 159 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.6 s to 1.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 15.2 MB in 90 requests on a phone: images 11.8 MB (51), scripts 2.7 MB (20) and HTML 351 KiB (1). Under 2 MB keeps phones on slow connections fast.

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

6 images are downloaded at several times the size a phone draws them, for example 170fb432-e6d2-4b21-bdd0-7f3543d12e69.png at 1,500 px wide, shown at 318 px. Resized copies would save about 2.5 MB.

9 images (3.9 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.

9 images further down the page (1.7 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 4.30 g of CO₂e: 515.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

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

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

Your meta description is only 25 characters: “Hispanic Scholarship Fund”. 70 to 160 characters is enough to sell the click.

There are 4 <h1> headlines (“Empowering Courageous Leaders”, “Our Partners” and “Making education a top priority”). 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 XML sitemap at https://www.hsf.net/sitemap.xml, so Google discovers your pages only by following links.

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

The homepage links to 22 pages on hsf.net and 0 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.

/corporate-partners/wells-fargo and /corporate-partners all use the title “Hispanic Scholarship Fund: Partners”. Search engines can't tell which page to show for a search, so each competes with the others.

/corporate-partners/wells-fargo, /support-hsf, /scholarship, /ways-to-volunteer, /event-calendar and /preparing-for-college and 9 others use the same meta description. A description written for each page earns more clicks.

/corporate-partners/wells-fargo, /support-hsf, /scholarship, /ways-to-volunteer, /event-calendar and /preparing-for-college and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

/scholarship-finder, /college-finder, /corporate-partners, /hsf-stories and /contact-us have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

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

http://hsf.net does not redirect to https, so some visitors land on the insecure version.

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.

hsf.net 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.

hsf.net'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.

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

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

There is no form on the homepage, so every lead has to click through to another page first.

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

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 Analytics, Google Tag Manager and Hotjar (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 5 cookies, 1 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 10 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.