Website review, no card needed
coanet.org website review
Visit site (opens in a new tab)Reviewed 21 October 202632 issues · 82 checks
This review found 32 issues worth fixing on coanet.org, 9 of them high impact, across 82 checks. The most urgent: reduce unused JavaScript. 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
84BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 2.4 s |
| May 9, 2026 | 2.4 s |
| May 16, 2026 | 2.4 s |
| May 23, 2026 | 2.2 s |
| May 30, 2026 | 2.2 s |
| Jun 6, 2026 | 2.1 s |
| Jun 13, 2026 | 2.1 s |
| Jun 20, 2026 | 2.2 s |
| Jun 27, 2026 | 2.2 s |
| Jul 4, 2026 | 2.2 s |
| Jul 11, 2026 | 2.4 s |
| Jul 18, 2026 | 2.4 s |
| Jul 25, 2026 | 2.4 s |
| Aug 1, 2026 | 2.5 s |
| Aug 8, 2026 | 2.5 s |
| Aug 15, 2026 | 2.4 s |
| Aug 22, 2026 | 2.4 s |
| Aug 29, 2026 | 2.2 s |
| Sep 5, 2026 | 2.2 s |
| Sep 12, 2026 | 2.1 s |
| Sep 19, 2026 | 1.9 s |
| Sep 26, 2026 | 1.9 s |
| Oct 3, 2026 | 2.1 s |
| Oct 10, 2026 | 2.0 s |
| Oct 17, 2026 | 2.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 116 ms |
| May 9, 2026 | 123 ms |
| May 16, 2026 | 121 ms |
| May 23, 2026 | 122 ms |
| May 30, 2026 | 127 ms |
| Jun 6, 2026 | 124 ms |
| Jun 13, 2026 | 127 ms |
| Jun 20, 2026 | 111 ms |
| Jun 27, 2026 | 95 ms |
| Jul 4, 2026 | 96 ms |
| Jul 11, 2026 | 113 ms |
| Jul 18, 2026 | 117 ms |
| Jul 25, 2026 | 152 ms |
| Aug 1, 2026 | 152 ms |
| Aug 8, 2026 | 144 ms |
| Aug 15, 2026 | 137 ms |
| Aug 22, 2026 | 119 ms |
| Aug 29, 2026 | 103 ms |
| Sep 5, 2026 | 95 ms |
| Sep 12, 2026 | 85 ms |
| Sep 19, 2026 | 111 ms |
| Sep 26, 2026 | 116 ms |
| Oct 3, 2026 | 114 ms |
| Oct 10, 2026 | 111 ms |
| Oct 17, 2026 | 95 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
Reduce unused JavaScript
5.1 s · 570 KiBAbout 570 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.1 s faster on a phone.
Render-blocking requests
4.1 s18 files block the first paint until they finish downloading. Deferring or inlining them could save about 4.1 s.
Reduce unused CSS
1.2 s · 229 KiBAbout 229 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.
Improve image delivery
600 ms · 611 KiB7 images could be 611 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 600 ms faster on a phone.
Mobile performance score: 56
56/100Your mobile performance score is 56 (desktop: 71). Pages that score under 90 lose visitors before the first paint.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Google CDN and Other Google APIs/SDKs and others), adding 1.4 MB and 749 ms of main-thread time.
Use efficient cache lifetimes
600 ms · 75 KiB6 files are served with short cache lifetimes, so returning visitors download them again (75 KiB).
Google Tag Manager adds 360 ms
360 msGoogle Tag Manager costs a phone 360 ms of main-thread work and 529 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 282 ms
282 msGoogle CDN costs a phone 282 ms of main-thread work and 733 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
170 ms · 15 KiB15 KiB could be saved by minifying JavaScript.
8 long tasks on the main thread
8 long tasks block the main thread while loading, the longest for 174 ms. During a long task the page ignores taps.
Font display
100 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).
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: 1.8 s
A phone's processor spends 1.8 s on main-thread work while loading, 1.2 s of it running JavaScript. That is comfortably low.
Server response: 20 ms
20 msYour server sent the HTML in 20 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.4 s
11.4 sThe first text or image appears after 11.4 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 20.3 s
20.3 sYour largest element takes 20.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “A Catalyst for Change Social Current is the premier partner…”.
Time to Interactive: 20.6 s
20.6 sThe page becomes fully interactive after 20.6 s. Good is under 3.8 s.
Speed Index: 11.4 s
11.4 sVisually, the page fills in at 11.4 s (Speed Index). Good is under 3.4 s.
Real-user FCP: 2.1 s
2.1 sReal visitors see the first content after 2.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.4 s
1.4 sReal visitors wait 1.4 s for your server to start answering (75th percentile). Good is under 800 ms.
8 images without width and height
8 images have no width and height attributes, so the layout jumps as each one loads.
7 checks passed
Real-user LCP: 2.0 s
2.0 sReal visitors wait 2.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 95 ms
95 msReal visitors wait 95 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 14% faster for real visitors
-14%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 116 ms to 95 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 15% faster for real visitors
-15%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.4 s to 2.0 s 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).
Total Blocking Time: 43 ms
43 msScripts block the page for only 43 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 3.5 MB in 96 requests
3.5 MBYour homepage downloads 3.5 MB in 96 requests on a phone: scripts 1.4 MB (29), images 909 KiB (22) and fonts 509 KiB (4). Under 2 MB keeps phones on slow connections fast.
6 images in older formats
6 images (698 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.
4 images far larger than shown
488 KiB4 images are downloaded at several times the size a phone draws them, for example iStock-2169063461-scaled.jpg at 1,920 px wide, shown at 130 px. Resized copies would save about 488 KiB.
4 images below the first screen load straight away
4 images further down the page (563 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.0 g of CO₂ per visit
0.99 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.99 g of CO₂e: 118.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
3 text elements with low contrast
3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
22 links without text
22 visible links have no text or label, so screen readers cannot say where they go.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
2 checks passed
Every image has alt text
All 15 images in the HTML carry an alt attribute.
46 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 2 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Meta description is long (163 characters)
Your meta description is 163 characters; Google truncates after about 160, so the end of your pitch is cut.
2 links crawlers can't follow
2 links have no real href, so search engines can't follow them.
59 internal links, 4 external
The homepage links to 59 pages on coanet.org and 4 external pages.
7 checks passed
One H1 headline
Your main headline reads: “A Catalyst for Change”.
Title: 58 characters
Your title is a healthy 58 characters: “Social Current | Activating the Power of the Social Sector”.
Canonical URL set
The canonical URL is https://www.social-current.org/.
Structured data in place
Structured data found: BreadcrumbList, ImageObject, Organization, WebPage and WebSite.
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.social-current.org/sitemap_index.xml.
AI search readiness
No llms.txt
There is no https://www.social-current.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: 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 (671 words), so crawlers that don't run JavaScript still read it.
Other pages
14 pages without a meta description
https://www.social-current.org/careers, https://www.social-current.org/contact, https://www.social-current.org/partnerships, https://www.social-current.org/the-hub, https://www.social-current.org/donate and https://www.social-current.org/coa-accreditation and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.
3 pages without an H1
https://www.social-current.org/donate, https://www.social-current.org/impact-partnerships and https://www.social-current.org/knowledge-and-insights-center/on-demand-learning have 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 35 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
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://data.stbuttons.click/data' from origin 'https://www.social-current.org' has been b…”.
2 checks passed
Tap targets are thumb-sized
7 of 7 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
Thin social proof
Social proof on the homepage: 8 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.
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 334 words of copy
The homepage carries about 334 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 About Social Current”.
5 calls to action
The homepage has 5 calls to action, for example “Contact”, “Learn More About Social Current” and “Learn More and Enroll”.
1 short form
A short form (1 field at most) is right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager.
Phone number on the homepage
Your phone number is on the homepage.
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 LinkedIn Insight (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 (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.
17 other companies contacted
Loading the homepage contacts 17 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 coanet.org, 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 32 issues on coanet.org, including 17 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.