Website review, no card needed
visd.net website review
Visit site (opens in a new tab)Reviewed 3 November 202645 issues · 85 checks
This review found 45 issues worth fixing on visd.net, 19 of them high impact, across 85 checks. The most urgent: improve image delivery. 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
68DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.1 s |
| May 23, 2026 | 2.1 s |
| May 30, 2026 | 2.1 s |
| Jun 6, 2026 | 2.0 s |
| Jun 13, 2026 | 1.9 s |
| Jun 20, 2026 | 1.9 s |
| Jun 27, 2026 | 1.8 s |
| Jul 4, 2026 | 1.8 s |
| Jul 11, 2026 | 1.8 s |
| Jul 18, 2026 | 1.7 s |
| Jul 25, 2026 | 1.7 s |
| Aug 1, 2026 | 1.7 s |
| Aug 8, 2026 | 1.7 s |
| Aug 15, 2026 | 1.7 s |
| Aug 22, 2026 | 1.8 s |
| Aug 29, 2026 | 1.8 s |
| Sep 5, 2026 | 1.8 s |
| Sep 12, 2026 | 1.9 s |
| Sep 19, 2026 | 1.9 s |
| Sep 26, 2026 | 1.9 s |
| Oct 3, 2026 | 1.9 s |
| Oct 10, 2026 | 1.9 s |
| Oct 17, 2026 | 1.9 s |
| Oct 24, 2026 | 2.0 s |
| Oct 31, 2026 | 2.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 179 ms |
| May 23, 2026 | 183 ms |
| May 30, 2026 | 188 ms |
| Jun 6, 2026 | 184 ms |
| Jun 13, 2026 | 180 ms |
| Jun 20, 2026 | 178 ms |
| Jun 27, 2026 | 171 ms |
| Jul 4, 2026 | 172 ms |
| Jul 11, 2026 | 166 ms |
| Jul 18, 2026 | 158 ms |
| Jul 25, 2026 | 156 ms |
| Aug 1, 2026 | 153 ms |
| Aug 8, 2026 | 159 ms |
| Aug 15, 2026 | 163 ms |
| Aug 22, 2026 | 164 ms |
| Aug 29, 2026 | 166 ms |
| Sep 5, 2026 | 172 ms |
| Sep 12, 2026 | 170 ms |
| Sep 19, 2026 | 172 ms |
| Sep 26, 2026 | 175 ms |
| Oct 3, 2026 | 165 ms |
| Oct 10, 2026 | 176 ms |
| Oct 17, 2026 | 180 ms |
| Oct 24, 2026 | 186 ms |
| Oct 31, 2026 | 214 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
Speed
Improve image delivery
11.7 s · 4.1 MB11 images could be 4.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 11.7 s faster on a phone.
Use efficient cache lifetimes
10.1 s · 2.9 MB29 files are served with short cache lifetimes, so returning visitors download them again (2.9 MB).
Reduce unused JavaScript
8.8 s · 2.2 MBAbout 2.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 8.8 s faster on a phone.
Mobile performance score: 33
33/100Your mobile performance score is 33. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
7,250 HTML elements
The page has 7,250 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Main-thread work: 4.5 s
A phone's processor spends 4.5 s on main-thread work while loading, 2.7 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 (YouTube, Google Tag Manager and Google CDN and others), adding 9.7 MB and 1.4 s of main-thread time.
Reduce unused CSS
600 ms · 358 KiBAbout 358 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 600 ms faster on a phone.
Render-blocking requests
900 ms6 files block the first paint until they finish downloading. Deferring or inlining them could save about 900 ms.
apptegy.net adds 46 ms
46 msapptegy.net costs a phone 46 ms of main-thread work and 6.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.
YouTube adds 461 ms
461 msYouTube costs a phone 461 ms of main-thread work and 1.1 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.
Google Tag Manager adds 417 ms
417 msGoogle Tag Manager costs a phone 417 ms of main-thread work and 798 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 CDN adds 290 ms
290 msGoogle CDN costs a phone 290 ms of main-thread work and 773 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 366 ms. During a long task the page ignores taps.
Legacy JavaScript
150 ms · 60 KiBPolyfills for old browsers add 60 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
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.
1 checks passed
Server response: 30 ms
30 msYour server sent the HTML in 30 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.
First Contentful Paint: 11.1 s
11.1 sThe first text or image appears after 11.1 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 38.6 s
38.6 sYour largest element takes 38.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Attendance Data Dashboard graphic”.
Speed Index: 18.1 s
18.1 sVisually, the page fills in at 18.1 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 47.8 s
47.8 sThe page becomes fully interactive after 47.8 s. Good is under 3.8 s.
Total Blocking Time: 1.0 s
1.0 sScripts block taps and scrolling for 1.0 s in total while the page loads. Good is under 200 ms.
Real-user INP: 254 ms
254 msReal visitors wait 254 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.12
0.12For real visitors the layout shifts by 0.12 (75th percentile). Good is under 0.1.
5 images without width and height
5 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 10% slower for real visitors
+10%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 179 ms to 214 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-6%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.1 s to 2.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user LCP: 1.7 s
1.7 sReal visitors wait 1.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 1.5 s
1.5 sReal visitors see the first content after 1.5 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 539 ms
539 msReal visitors wait 539 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 11.4 MB in 187 requests
11.4 MBYour homepage downloads 11.4 MB in 187 requests on a phone: images 5.2 MB (24), scripts 4.1 MB (33) and other files 1.3 MB (114). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
81b160aa-ac2b-4355-a849-fe8e94e639ab.jpeg weighs 1.8 MB. On a phone connection a single image that size takes seconds.
2 images far larger than shown
2.0 MB2 images are downloaded at several times the size a phone draws them, for example 81b160aa-ac2b-4355-a849-fe8e94e639ab.jpeg at 4,032 px wide, shown at 390 px. Resized copies would save about 2.0 MB.
8 images in older formats
8 images (3.4 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.
1 image below the first screen load straight away
1 image further down the page (1.8 MB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 3.2 g of CO₂ per visit
3.24 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.24 g of CO₂e: 389.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Invalid ARIA attributes
1 element use ARIA attributes their role does not allow, which confuses screen readers.
Images must have alternative text (1 element)
Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.
Elements must only use permitted ARIA attributes (1 element)
Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.
Heading levels should only increase by one (1 element)
Heading levels should only increase by one: 1 element on the page fails 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.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
1 checks passed
46 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 4 failed. 5 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
Meta description is short (28 characters)
Your meta description is only 28 characters: “Achieving Excellence For All”. 70 to 160 characters is enough to sell the click.
3 links with vague text
3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
231 internal links, 24 external
The homepage links to 231 pages on visd.net and 24 external pages.
6 checks passed
One H1 headline
Your main headline reads: “Victoria Independent School District”.
Title: 43 characters
Your title is a healthy 43 characters: “Home | Victoria Independent School District”.
Canonical URL set
The canonical URL is https://www.visd.net/.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
robots.txt in place
robots.txt is in place.
XML sitemap found
Your XML sitemap is reachable at https://www.visd.net/sitemap.xml.
AI search readiness
No Organization structured data
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.
No llms.txt
There is no https://www.visd.net/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.
2 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.
Text is in the HTML
Your server sends the page's text in the HTML (883 words), so crawlers that don't run JavaScript still read it.
Other pages
5 pages share a title
https://www.visd.net/browse/238344, https://www.visd.net/browse/238211, https://www.visd.net/documents/about-visd/school-board/board-resolutions/22213772, https://www.visd.net/browse/281198 and https://www.visd.net/browse/238241 all use the title “Documents | Victoria Independent School District”. Search engines can't tell which page to show for a search, so each competes with the others.
15 pages without a meta description
https://www.visd.net/page/parent-gradebook, https://www.visd.net/browse/238344, https://www.visd.net/page/contact-us, https://www.visd.net/page/about-visd, https://www.visd.net/page/school-board and https://www.visd.net/page/procedures-ethics-maps and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.
15 pages without an H1
https://www.visd.net/page/parent-gradebook, https://www.visd.net/browse/238344, https://www.visd.net/page/contact-us, https://www.visd.net/page/about-visd, https://www.visd.net/page/school-board and https://www.visd.net/page/procedures-ethics-maps and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.
4 pages slow to respond
https://www.visd.net/browse/238211, https://www.visd.net/browse/281198, https://www.visd.net/browse/238241 and https://www.visd.net/page/upcoming-meetings-and-agendas took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 197 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.
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
5 third-party cookies
5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Hydration completed but contains mismatches.”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
2 checks passed
Tap targets are thumb-sized
28 of 29 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 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 form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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 746 words of copy
The homepage carries about 746 words of visible text.
3 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Contact Us”.
6 calls to action
The homepage has 6 calls to action, for example “Contact Us”, “Transcript Request” and “Service Records Request”.
Analytics in place
Analytics detected: Google Tag Manager and Google Analytics.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Meta Pixel (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.
6 cookies set on arrival
6Opening the homepage sets 6 cookies, 1 of them by other companies (measured from a US location before any click).
No consent tool detected
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.
31 other companies contacted
Loading the homepage contacts 31 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
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 visd.net, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Nuxt
- Analytics
- Google Analytics | Google Tag Manager
- Hosting
- AWS
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 45 issues on visd.net, including 23 speed issues, 3 SEO issues and 2 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.