kasasa.com website review

The page goes through 1 redirect before it starts loading, costing about 14.6 s. Link and advertise the final URL directly.

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

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

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

2 files block the first paint until they finish downloading. Deferring or inlining them could save about 550 ms.

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

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

8 third-party services load with your homepage (Google Analytics, cptn.co and Google Tag Manager and others), adding 14 KiB and 187 ms of main-thread time.

1 image could be 15 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

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 25.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “This site is intended for US based customers only.”.

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

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

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

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

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

Real visitors wait 1.5 s for your server to start answering (75th percentile). Good is under 800 ms.

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

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

Your homepage downloads 4.1 MB in 115 requests on a phone: scripts 2.5 MB (48), images 912 KiB (19) and fonts 315 KiB (7). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example surelock-phone.png at 618 px wide, shown at 130 px. Resized copies would save about 36 KiB.

1 image further down the page (59 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

2 buttons have no accessible name, so screen readers announce just “button”.

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

ARIA commands must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

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

The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

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

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

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

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

The homepage links to 91 pages on kasasa.com and 11 external pages.

https://www.kasasa.com/offer-kasasa-1 declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

/ and https://www.kasasa.com/offer-kasasa-1 all use the title “Offer Kasasa at your Institution | Kasasa”. Search engines can't tell which page to show for a search, so each competes with the others.

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

4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 403 ()”.

Large scripts ship without source maps.

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

The homepage carries about 2,735 words of visible text.

The page uses urgency cues (a countdown or limited-time wording).

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and LinkedIn Insight and 1 more (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 19 cookies, 2 of them by other companies (measured from a US location before any click).

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