Website review, no card needed
islandinstitute.org website review
Visit site (opens in a new tab)Reviewed 25 October 202637 issues · 85 checks
This review found 37 issues worth fixing on islandinstitute.org, 16 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
77CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 1.9 s |
| May 9, 2026 | 1.9 s |
| May 16, 2026 | 2.0 s |
| May 23, 2026 | 2.0 s |
| May 30, 2026 | 2.0 s |
| Jun 6, 2026 | 2.0 s |
| Jun 13, 2026 | 2.0 s |
| Jun 20, 2026 | 2.1 s |
| Jun 27, 2026 | 2.1 s |
| Jul 4, 2026 | 2.1 s |
| Jul 11, 2026 | 2.1 s |
| Jul 18, 2026 | 2.1 s |
| Jul 25, 2026 | 2.1 s |
| Aug 1, 2026 | 2.1 s |
| Aug 8, 2026 | 2.1 s |
| Aug 15, 2026 | 2.2 s |
| Aug 22, 2026 | 2.2 s |
| Aug 29, 2026 | 2.3 s |
| Sep 5, 2026 | 2.4 s |
| Sep 12, 2026 | 2.5 s |
| Sep 19, 2026 | 2.5 s |
| Sep 26, 2026 | 2.5 s |
| Oct 3, 2026 | 2.6 s |
| Oct 10, 2026 | 2.6 s |
| Oct 17, 2026 | 2.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 90 ms |
| May 9, 2026 | 91 ms |
| May 16, 2026 | 90 ms |
| May 23, 2026 | 89 ms |
| May 30, 2026 | 88 ms |
| Jun 6, 2026 | 87 ms |
| Jun 13, 2026 | 89 ms |
| Jun 20, 2026 | 89 ms |
| Jun 27, 2026 | 90 ms |
| Jul 4, 2026 | 87 ms |
| Jul 11, 2026 | 80 ms |
| Jul 18, 2026 | 81 ms |
| Jul 25, 2026 | 83 ms |
| Aug 1, 2026 | 82 ms |
| Aug 8, 2026 | 84 ms |
| Aug 15, 2026 | 87 ms |
| Aug 22, 2026 | 87 ms |
| Aug 29, 2026 | 95 ms |
| Sep 5, 2026 | 96 ms |
| Sep 12, 2026 | 95 ms |
| Sep 19, 2026 | 94 ms |
| Sep 26, 2026 | 88 ms |
| Oct 3, 2026 | 87 ms |
| Oct 10, 2026 | 82 ms |
| Oct 17, 2026 | 79 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.7 s
3.1 s
Speed
Improve image delivery
8.2 s · 1.5 MB4 images could be 1.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 8.2 s faster on a phone.
Use efficient cache lifetimes
2.4 s · 412 KiB27 files are served with short cache lifetimes, so returning visitors download them again (412 KiB).
Reduce unused JavaScript
1.6 s · 332 KiBAbout 332 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.6 s faster on a phone.
Render-blocking requests
1.2 s15 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.2 s.
Mobile performance score: 46
46/100Your mobile performance score is 46 (desktop: 84). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Facebook and Hotjar and others), adding 1.1 MB and 958 ms of main-thread time.
Google Tag Manager adds 500 ms
500 msGoogle Tag Manager costs a phone 500 ms of main-thread work and 526 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
400 ms · 12 KiBPolyfills for old browsers add 12 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 400 ms faster on a phone.
9 long tasks on the main thread
9 long tasks block the main thread while loading, the longest for 203 ms. During a long task the page ignores taps.
Reduce unused CSS
150 ms · 38 KiBAbout 38 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
Phones get a much slower page than desktops
Desktop scores 84 but mobile only 46. A gap that wide usually means heavy scripts and images that hit phones hardest.
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.
2 checks passed
Main-thread work: 2.0 s
A phone's processor spends 2.0 s on main-thread work while loading, 1.1 s of it running JavaScript. That is comfortably low.
Server response: 59 ms
59 msYour server sent the HTML in 59 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: 7.9 s
7.9 sThe first text or image appears after 7.9 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 22.7 s
22.7 sYour largest element takes 22.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “COMMUNITY INNOVATION FOR A STRONGER MAINE COAST LEARN MORE …”.
Time to Interactive: 22.7 s
22.7 sThe page becomes fully interactive after 22.7 s. Good is under 3.8 s.
Speed Index: 9.3 s
9.3 sVisually, the page fills in at 9.3 s (Speed Index). Good is under 3.4 s.
Real-user LCP: 2.5 s
2.5 sReal visitors wait 2.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Largest content (LCP) got 31% slower for real visitors
+31%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 1.9 s to 2.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 2.2 s
2.2 sReal visitors see the first content after 2.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.7 s
1.7 sReal visitors wait 1.7 s for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 430 ms
430 msScripts block taps and scrolling for 430 ms in total while the page loads. Good is under 200 ms.
4 checks passed
Real-user INP: 80 ms
80 msReal visitors wait 80 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Tap response (INP) got 11% faster for real visitors
-11%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 90 ms to 79 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
1 image over 500 KB
Orange-ring-Priorities2.png weighs 605 KiB. On a phone connection a single image that size takes seconds.
Page weight: 3.6 MB in 100 requests
3.6 MBYour homepage downloads 3.6 MB in 100 requests on a phone: images 2.2 MB (12), scripts 1.0 MB (45) and fonts 218 KiB (8). Under 2 MB keeps phones on slow connections fast.
3 images in older formats
3 images (1.5 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 1.0 g of CO₂ per visit
1.02 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.02 g of CO₂e: 122.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
6 text elements with low contrast
6 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
ARIA input fields must have an accessible name (1 element)
ARIA input fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.
Interactive controls must not be nested (1 element)
Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.
3 images without alt text
3 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (5 elements)
All page content should be contained by landmarks: 5 elements on the page fail this check, rated moderate by axe-core.
31 links without text
31 visible links have no text or label, so screen readers cannot say where they go.
Alternative text of images should not be repeated as text (4 elements)
Alternative text of images should not be repeated as text: 4 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h1 → h3), 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 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 8 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (66 characters)
Your title is 66 characters, so Google will cut it off around 60: “Island Institute - Community Innovation for a Stronger Maine Coast”.
8 links with vague text
8 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
117 internal links, 21 external
The homepage links to 117 pages on islandinstitute.org and 21 external pages.
7 checks passed
Meta description: 129 characters
Your meta description is 129 characters: “We boldly navigate climate and economic change with island and coastal communities to expand opportunities and deliver …”.
One H1 headline
Your main headline reads: “Community Innovation for a Stronger Maine Coast”.
Canonical URL set
The canonical URL is https://www.islandinstitute.org/.
Structured data in place
Structured data found: Article, ImageObject, Organization, Place and WebPage.
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 and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://www.islandinstitute.org/sitemap_index.xml.
AI search readiness
No llms.txt
There is no https://www.islandinstitute.org/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.
3 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: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (1,495 words), so crawlers that don't run JavaScript still read it.
Other pages
11 pages without a meta description
https://www.islandinstitute.org/stories/the-working-waterfront, https://www.islandinstitute.org/priorities, https://www.islandinstitute.org/priorities/marine-economy, https://www.islandinstitute.org/priorities/marine-economy/working-waterfront-protection, https://www.islandinstitute.org/priorities/marine-economy/climate-forward-marine-economy and https://www.islandinstitute.org/priorities/climate-solutions and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://www.islandinstitute.org/stories/the-working-waterfront 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 66 found) and read each the way a search engine does.
5 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.
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
30 small tap targets
30 of 65 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
1 checks passed
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.
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 opening hours
The homepage shows no opening hours. If customers visit or call, show when.
Phone number is not tap-to-call
Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.
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,331 words of copy
The homepage carries about 1,331 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: “LEARN MORE & JOIN US”.
15 calls to action
The homepage has 15 calls to action, for example “Apply for Grants and Scholarships”, “Contact Us” and “Learn More & Join Us”.
1 short form
A short form (1 field at most) is right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and Hotjar.
Phone number on the homepage
Your phone number is on the homepage.
Privacy and tracking
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and LinkedIn Insight and 2 mores (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.
13 cookies set on arrival
13Opening the homepage sets 13 cookies (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.
25 other companies contacted
Loading the homepage contacts 25 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 islandinstitute.org, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- WordPress
- Framework
- jQuery
- Analytics
- Google Analytics | Google Tag Manager | Hotjar
Company
- Founded
- 1983
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 37 issues on islandinstitute.org, including 18 speed issues, 2 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.