Website review, no card needed
torontofilmschool.ca website review
Visit site (opens in a new tab)Reviewed 19 November 202646 issues · 91 checks
This review found 46 issues worth fixing on torontofilmschool.ca, 16 of them high impact, across 91 checks. The most urgent: calendly adds 2.5 s. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
70CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 3.6 s |
| Jun 6, 2026 | 3.8 s |
| Jun 13, 2026 | 3.9 s |
| Jun 20, 2026 | 3.9 s |
| Jun 27, 2026 | 3.9 s |
| Jul 4, 2026 | 3.8 s |
| Jul 11, 2026 | 3.6 s |
| Jul 18, 2026 | 3.3 s |
| Jul 25, 2026 | 3.3 s |
| Aug 1, 2026 | 3.3 s |
| Aug 8, 2026 | 3.3 s |
| Aug 15, 2026 | 3.2 s |
| Aug 22, 2026 | 3.2 s |
| Aug 29, 2026 | 3.2 s |
| Sep 5, 2026 | 3.1 s |
| Sep 12, 2026 | 3.0 s |
| Sep 19, 2026 | 3.1 s |
| Sep 26, 2026 | 3.1 s |
| Oct 3, 2026 | 3.0 s |
| Oct 10, 2026 | 3.1 s |
| Oct 17, 2026 | 3.3 s |
| Oct 24, 2026 | 3.5 s |
| Oct 31, 2026 | 3.6 s |
| Nov 7, 2026 | 3.6 s |
| Nov 14, 2026 | 3.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 170 ms |
| Jun 6, 2026 | 177 ms |
| Jun 13, 2026 | 181 ms |
| Jun 20, 2026 | 182 ms |
| Jun 27, 2026 | 181 ms |
| Jul 4, 2026 | 180 ms |
| Jul 11, 2026 | 178 ms |
| Jul 18, 2026 | 172 ms |
| Jul 25, 2026 | 179 ms |
| Aug 1, 2026 | 177 ms |
| Aug 8, 2026 | 176 ms |
| Aug 15, 2026 | 171 ms |
| Aug 22, 2026 | 172 ms |
| Aug 29, 2026 | 181 ms |
| Sep 5, 2026 | 188 ms |
| Sep 12, 2026 | 195 ms |
| Sep 19, 2026 | 194 ms |
| Sep 26, 2026 | 204 ms |
| Oct 3, 2026 | 220 ms |
| Oct 10, 2026 | 240 ms |
| Oct 17, 2026 | 275 ms |
| Oct 24, 2026 | 285 ms |
| Oct 31, 2026 | 297 ms |
| Nov 7, 2026 | 303 ms |
| Nov 14, 2026 | 276 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
How it loaded on a phone
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Calendly adds 2.5 s
2.5 sCalendly costs a phone 2.5 s of main-thread work and 9.6 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Render-blocking requests
1.2 s10 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.2 s.
Main-thread work: 10.3 s
A phone's processor spends 10.3 s on main-thread work while loading, 5.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (Calendly, Stripe and Google Tag Manager and others), adding 12.4 MB and 4.3 s of main-thread time.
Reduce unused JavaScript
5.3 MBAbout 5.3 MB of JavaScript is downloaded but never used on this page.
Use efficient cache lifetimes
1.7 MB38 files are served with short cache lifetimes, so returning visitors download them again (1.7 MB).
Reduce unused CSS
1.4 MBAbout 1.4 MB of CSS is downloaded but never applied on this page.
Mobile performance score: 55
55/100Your mobile performance score is 55. Pages that score under 90 lose visitors before the first paint.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 930 ms. During a long task the page ignores taps.
Stripe adds 409 ms
409 msStripe costs a phone 409 ms of main-thread work and 855 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.
Drift adds 314 ms
314 msDrift costs a phone 314 ms of main-thread work and 812 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 Tag Manager adds 332 ms
332 msGoogle Tag Manager costs a phone 332 ms of main-thread work and 509 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.
Minify JavaScript
101 KiB101 KiB could be saved by minifying JavaScript.
Legacy JavaScript
92 KiBPolyfills for old browsers add 92 KiB JavaScript that modern phones do not need.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Improve image delivery
13 KiB1 image could be 13 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Minify CSS
6 KiB6 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: 3 ms
3 msYour server sent the HTML in 3 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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.
Real-user TTFB: 1.9 s
1.9 sReal visitors wait 1.9 s for your server to start answering (75th percentile). Good is under 800 ms.
Speed Index: 22.0 s
22.0 sVisually, the page fills in at 22.0 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 102.5 s
102.5 sThe page becomes fully interactive after 102.5 s. Good is under 3.8 s.
Total Blocking Time: 3.1 s
3.1 sScripts block taps and scrolling for 3.1 s in total while the page loads. Good is under 200 ms.
Real-user LCP: 3.7 s
3.7 sReal visitors wait 3.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 309 ms
309 msReal visitors wait 309 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 67% slower for real visitors
+67%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 170 ms to 276 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 2.6 s
2.6 sReal visitors see the first content after 2.6 s (75th percentile). Good is under 1.8 s.
First Contentful Paint: 2.5 s
2.5 sThe first text or image appears after 2.5 s on a phone. Good is under 1.8 s.
33 images without width and height
33 images have no width and height attributes, so the layout jumps as each one loads.
Largest Contentful Paint: 2.5 s
2.5 sYour largest element takes 2.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “CHOOSE YOUR PROGRAM & BUILD A KILLER PORTFOLIO”. Most of its time is element render delay (2.3 s).
Largest content (LCP) held steady for real visitors
-6%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 3.6 s to 3.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
Real-user CLS: 0.09
0.09For real visitors the layout shifts by 0.09 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 29.2 MB in 327 requests
29.2 MBYour homepage downloads 29.2 MB in 327 requests on a phone: scripts 9.8 MB (135), media 8.5 MB (1) and images 6.7 MB (93). Under 2 MB keeps phones on slow connections fast.
24 images far larger than shown
3.2 MB24 images are downloaded at several times the size a phone draws them, for example Ready-Player-one.jpg at 1,080 px wide, shown at 205 px. Resized copies would save about 3.2 MB.
30 images below the first screen load straight away
30 images further down the page (5.0 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
24 images in older formats
24 images (4.7 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.
About 8.3 g of CO₂ per visit
8.28 gBy the Sustainable Web Design model, a visit to your homepage emits about 8.28 g of CO₂e: 993.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
2 buttons without a name
2 buttons have no accessible name, so screen readers announce just “button”.
Scrollable region must have keyboard access (1 element)
Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.
33 images without alt text
33 images have no alt text, which hurts accessibility and image search.
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.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
12 links without text
12 visible links have no text or label, so screen readers cannot say where they go.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (3 elements).
1 checks passed
43 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 49 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 passed and 6 failed. 6 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
11 links with vague text
11 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
110 internal links, 22 external
The homepage links to 110 pages on torontofilmschool.ca and 22 external pages.
6 checks passed
Meta description: 135 characters
Your meta description is 135 characters: “Experience a real-world curriculum, make valuable connections, and graduate industry ready in just 12–18 months at Toro…”.
Title: 64 characters
Your title is a healthy 64 characters: “Industry-Focused Creative Diploma Programs | Toronto Film School”.
Canonical URL set
The canonical URL is https://www.torontofilmschool.ca/.
Structured data in place
Structured data found: BreadcrumbList, Organization, SiteNavigationElement, WebPage and WebSite.
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://staging.torontofilmschool.ca/sitemap_index.xml.
AI search readiness
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: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (1,373 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.torontofilmschool.ca/llms.txt (2 KiB, 10 links), a plain-text guide to the site for AI tools.
Other pages
1 linked page hidden from search
https://www.torontofilmschool.ca/academy is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
1 page without a meta description
https://www.torontofilmschool.ca/tfs-referral-program has no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://www.torontofilmschool.ca/academy has no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 47 found) and read each the way a search engine does.
4 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.
Titles are unique
Every page we checked has its own title.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
1 broken image
1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=5751737&tm=gtm002&Ver=2&mid=1b65c832-23e2-4252-808e-0e0db6e8dbff&bo=1&sid=6c43b030e44711f198b56f93e6b3f616&vid=6c43af00e44711f1913d350f9b1ece00&vids=1&msclkid=N&pi=918.
2 third-party cookies
2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Fenced Frame API is deprecated and scheduled for removal.”).
5 JavaScript errors while loading
5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
Missing source maps
Large scripts ship without source maps.
2 checks passed
Tap targets are thumb-sized
14 of 17 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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,156 words of copy
The homepage carries about 1,156 words of visible text.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “REQUEST INFO” and “APPLY NOW”.
19 calls to action
The homepage has 19 calls to action, for example “Book a Consultation”, “Call us Directly” and “Learn More”.
4 short forms
4 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 1 phone link and 0 email links.
Privacy and tracking
8 trackers load before any consent
8Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Ads and 3 mores (measured from a US location before any click). A consent tool (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.
31 cookies set on arrival
31Opening the homepage sets 31 cookies, 2 of them by other companies (measured from a US location before any click).
49 other companies contacted
Loading the homepage contacts 49 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: CookieYes
A consent management tool (CookieYes) 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 torontofilmschool.ca, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Go beyond the website
What your $25 Growth Playbook adds
This review found 46 issues on torontofilmschool.ca, including 24 speed issues, 3 SEO issues and 1 conversion gap. 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.