skyward.com website review

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

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

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

251 KiB could be saved by minifying JavaScript.

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

The page has 3,679 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

22 images could be 631 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 750 ms faster on a phone.

Your mobile performance score is 55 (desktop: 73). Pages that score under 90 lose visitors before the first paint.

8 third-party services load with your homepage (Google Tag Manager, JSDelivr CDN and Pardot and others), adding 1.0 MB and 327 ms of main-thread time.

69 KiB could be saved by minifying CSS.

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

Google Tag Manager costs a phone 298 ms of main-thread work and 321 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.

Google Fonts costs a phone 0 ms of main-thread work and 607 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.

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

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

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

14 KiB JavaScript is shipped twice across bundles.

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.

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

Your largest element takes 18.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Teacher and students”.

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

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

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

29 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-03, real Chrome visitors' tap response (inp) went from 84 ms to 87 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 4.0 MB in 125 requests on a phone: images 1.3 MB (80), scripts 1.3 MB (26) and fonts 653 KiB (4). Under 2 MB keeps phones on slow connections fast.

6 images (765 KiB) 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.

13 images further down the page (643 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

1 image is downloaded at several times the size a phone draws it, for example greatetsthitsbTS-2026-small-card-1.webp at 1,280 px wide, shown at 351 px. Resized copies would save about 21 KiB.

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

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

4 elements have a tabindex above 0, which scrambles the keyboard order.

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

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

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

Alternative text of images should not be repeated as text: 5 elements on the page fail this check, rated minor by axe-core.

Your meta description is 201 characters; Google truncates after about 160, so the end of your pitch is cut.

Structured data found (untyped) but with 1 problem, for example “ld+json block 1 is not valid JSON (Unexpected end of JSON input)”.

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

There is no robots.txt at skyward.com/robots.txt, the first file search crawlers ask for.

13 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

10 links have no real href, so search engines can't follow them.

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

The homepage links to 210 pages on skyward.com and 10 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.

/home 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 /home all use the title “Skyward | A Better SIS and ERP Experience”. 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 104 found) and read each the way a search engine does.

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

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

skyward.com'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.

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

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.

The homepage carries about 575 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 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 (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.