Website review, no card needed

instructure.com logo

instructure.com website review

Visit site (opens in a new tab)Reviewed 29 October 202636 issues · 85 checks

This review found 36 issues worth fixing on instructure.com, 11 of them high impact, across 85 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
3.9 s2.5 sMay 9Oct 243.1 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20263.0 s
May 16, 20262.8 s
May 23, 20262.8 s
May 30, 20262.8 s
Jun 6, 20263.0 s
Jun 13, 20263.4 s
Jun 20, 20263.6 s
Jun 27, 20263.7 s
Jul 4, 20263.7 s
Jul 11, 20263.7 s
Jul 18, 20263.5 s
Jul 25, 20263.4 s
Aug 1, 20263.3 s
Aug 8, 20263.2 s
Aug 15, 20263.1 s
Aug 22, 20263.0 s
Aug 29, 20262.8 s
Sep 5, 20262.7 s
Sep 12, 20262.7 s
Sep 19, 20262.7 s
Sep 26, 20262.8 s
Oct 3, 20262.9 s
Oct 10, 20263.0 s
Oct 17, 20263.0 s
Oct 24, 20263.1 s
Real-visitor tap response (INP)75th percentile, phones
300 ms215 msMay 9Oct 24283 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026234 ms
May 16, 2026225 ms
May 23, 2026225 ms
May 30, 2026225 ms
Jun 6, 2026252 ms
Jun 13, 2026265 ms
Jun 20, 2026267 ms
Jun 27, 2026264 ms
Jul 4, 2026270 ms
Jul 11, 2026277 ms
Jul 18, 2026281 ms
Jul 25, 2026288 ms
Aug 1, 2026290 ms
Aug 8, 2026289 ms
Aug 15, 2026281 ms
Aug 22, 2026269 ms
Aug 29, 2026261 ms
Sep 5, 2026258 ms
Sep 12, 2026258 ms
Sep 19, 2026260 ms
Sep 26, 2026260 ms
Oct 3, 2026267 ms
Oct 10, 2026270 ms
Oct 17, 2026275 ms
Oct 24, 2026283 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of instructure.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. instructure.com at 0.4 s0.4 s
  2. instructure.com at 0.8 s0.8 s
  3. instructure.com at 1.2 s1.2 s
  4. instructure.com at 1.6 s1.6 s
  5. instructure.com at 1.9 s1.9 s
  6. instructure.com at 2.3 s2.3 s
  7. instructure.com at 2.7 s2.7 s
  8. instructure.com at 3.1 s3.1 s

Speed

11 to fix52
  • Render-blocking requests

    5.8 s

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

  • Reduce unused JavaScript

    2.5 s · 495 KiB

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

  • Reduce unused CSS

    1.2 s · 248 KiB

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

  • Mobile performance score: 52

    52/100

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

  • Use efficient cache lifetimes

    850 ms · 125 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Wistia and Optanon and others), adding 1.2 MB and 749 ms of main-thread time.

  • Google Tag Manager adds 398 ms

    398 ms

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

  • Legacy JavaScript

    300 ms · 20 KiB

    Polyfills for old browsers add 20 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.

  • Main-thread work: 2.7 s

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

  • 2,529 HTML elements

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

  • Wistia adds 199 ms

    199 ms

    Wistia costs a phone 199 ms of main-thread work and 317 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.

  • 9 long tasks on the main thread

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

  • Minify JavaScript

    150 ms · 20 KiB

    20 KiB could be saved by minifying JavaScript.

  • Improve image delivery

    44 KiB

    2 images could be 44 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Minify CSS

    25 KiB

    25 KiB could be saved by minifying CSS.

  • Chained critical requests

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

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

1 checks passed
  • Server response: 5 ms

    5 ms

    Your server sent the HTML in 5 ms, well inside Google's 600 ms guideline.

Core Web Vitals

10 to fix33
  • Fails Core Web Vitals for real visitors

    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.

  • First Contentful Paint: 10.2 s

    10.2 s

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

  • Largest Contentful Paint: 17.6 s

    17.6 s

    Your largest element takes 17.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Edtech Top 40”.

  • Time to Interactive: 17.7 s

    17.7 s

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

  • Speed Index: 10.2 s

    10.2 s

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

  • Real-user LCP: 2.5 s

    2.5 s

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

  • Real-user INP: 251 ms

    251 ms

    Real visitors wait 251 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

    +22%

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

  • Real-user FCP: 2.0 s

    2.0 s

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

  • Total Blocking Time: 238 ms

    238 ms

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

  • Largest content (LCP) held steady for real visitors

    +4%

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

3 checks passed
  • Real-user CLS: 0.05

    0.05

    For real visitors the layout shifts by 0.05 (75th percentile). Good is under 0.1.

  • Real-user TTFB: 602 ms

    602 ms

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

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

2 to fix81
  • Page weight: 2.6 MB in 182 requests

    2.6 MB

    Your homepage downloads 2.6 MB in 182 requests on a phone: scripts 1.3 MB (68), stylesheets 608 KiB (66) and images 512 KiB (30). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    rr-hcr-oct26-p04-screen_time.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • About 0.8 g of CO₂ per visit

    0.75 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

3 to fixGoogle 10096
  • 16 images without alt text

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

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

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

  • 1 form field without a label

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

  • Headings skip levels

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

1 checks passed
  • 45 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 46 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 1 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 9294
  • 34 links with vague text

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

  • Structured data has 1 problem

    Structured data found (Organization and WebPage) but with 1 problem, for example “WebPage: breadcrumb is an empty list”.

  • Open Graph partly set

    Open Graph is missing og:description, so shared links fall back to guesses.

  • No X (Twitter) card tag

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

  • 144 internal links, 16 external

    The homepage links to 144 pages on instructure.com and 16 external pages.

6 checks passed
  • Meta description: 159 characters

    Your meta description is 159 characters: “Empower learning with Instructure’s LMS and edtech solutions for K–12, higher education, and businesses. Discover Canva…”.

  • One H1 headline

    Your main headline reads: “Welcome to the most-visited education website in the world.”.

  • Title: 58 characters

    Your title is a healthy 58 characters: “Instructure: Leading EdTech for K–12, Higher Ed & Business”.

  • Canonical URL set

    The canonical URL is https://www.instructure.com/.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.instructure.com/sitemap.xml.

AI search readiness

100
4 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Organization data: 6 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,867 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://www.instructure.com/llms.txt (195 KiB, 1,369 links), a plain-text guide to the site for AI tools.

Other pages

1 to fix93
  • 2 pages share a title

    / and https://www.instructure.com/ko all use the title “Instructure: Leading EdTech for K–12, Higher Ed & Business”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 15 internal pages checked

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

6 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

3 to fixGoogle 10071
  • 2 broken images

    2 images failed to load on a phone, for example https://bat.bing.com/action/0?ti=187051609&tm=gtm002&Ver=2&mid=dbbb6cb5-3844-410c-a0d3-1425b3ba7f99&bo=1&sid=be109990d34811f1a4217152ab6ac3e5&vid=be10cf60d34811f19bd9ebd559046234&vids=1&msclkid=N&gtm_.

  • 8 small tap targets

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

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Munchkin is not defined”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix69
  • 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.

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

  • No phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • No direct contact details

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

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

  • About 1,699 words of copy

    The homepage carries about 1,699 words of visible text.

4 checks passed
  • 28 calls to action

    The homepage has 28 calls to action, for example “Learn more”, “Learn More” and “Apply”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 6 testimonial or review blocks, 17 customer or partner logos, 8 trust badges and “8000+ customers”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

  • 9 trackers load before any consent

    9

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

  • 20 cookies set on arrival

    20

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

  • 57 other companies contacted

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

1 checks passed
  • Consent tool: OneTrust

    A consent management tool (OneTrust) loads with the page.

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at instructure.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
Drupal
Framework
jQuery
Analytics
Google Tag Manager
Hosting
Fastly

Hiring

Hiring
57 open roles
Teams
Sales & Marketing (25), Research & Development (17), Client Services (9), General & Administration (5)
Job board
ashby

Company

Employees
1,240
Founded
2008
Headquarters
Salt Lake City

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 36 issues on instructure.com, including 21 speed issues, 2 SEO issues and 4 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25