Website review, no card needed

servicecoord.org logo

servicecoord.org website review

Visit site (opens in a new tab)Reviewed 28 October 202618 issues · 70 checks

This review found 18 issues worth fixing on servicecoord.org, 6 of them high impact, across 70 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
902 ms675 msMay 9Oct 24806 ms
Show as table
DateReal-visitor load time (LCP)
May 9, 2026763 ms
May 16, 2026747 ms
May 23, 2026801 ms
May 30, 2026876 ms
Jun 6, 2026714 ms
Jun 13, 2026705 ms
Jun 20, 2026701 ms
Jun 27, 2026701 ms
Jul 4, 2026847 ms
Jul 11, 2026781 ms
Jul 18, 2026798 ms
Jul 25, 2026794 ms
Aug 1, 2026786 ms
Aug 8, 2026860 ms
Aug 15, 2026800 ms
Aug 22, 2026759 ms
Aug 29, 2026798 ms
Sep 5, 2026757 ms
Sep 12, 2026785 ms
Sep 19, 2026808 ms
Sep 26, 2026814 ms
Oct 3, 2026819 ms
Oct 10, 2026876 ms
Oct 17, 2026843 ms
Oct 24, 2026806 ms
Real-visitor tap response (INP)75th percentile, phones
100 ms74 msMay 9Oct 2487 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 202687 ms
May 16, 202687 ms
May 23, 202694 ms
May 30, 202697 ms
Jun 6, 202690 ms
Jun 13, 202687 ms
Jun 20, 202684 ms
Jun 27, 202677 ms
Jul 4, 202679 ms
Jul 11, 202679 ms
Jul 18, 202679 ms
Jul 25, 202679 ms
Aug 1, 202680 ms
Aug 8, 202685 ms
Aug 15, 202680 ms
Aug 22, 202683 ms
Aug 29, 202681 ms
Sep 5, 202680 ms
Sep 12, 202686 ms
Sep 19, 202686 ms
Sep 26, 202687 ms
Oct 3, 202692 ms
Oct 10, 202688 ms
Oct 17, 202688 ms
Oct 24, 202687 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 servicecoord.org (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. servicecoord.org at 0.4 s0.4 s
  2. servicecoord.org at 0.8 s0.8 s
  3. servicecoord.org at 1.1 s1.1 s
  4. servicecoord.org at 1.5 s1.5 s
  5. servicecoord.org at 1.9 s1.9 s
  6. servicecoord.org at 2.3 s2.3 s
  7. servicecoord.org at 2.6 s2.6 s
  8. servicecoord.org at 3.0 s3.0 s

Speed

5 to fix60
  • Render-blocking requests

    2.3 s

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

  • Reduce unused JavaScript

    900 ms · 142 KiB

    About 142 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 900 ms faster on a phone.

  • Mobile performance score: 60

    60/100

    Your mobile performance score is 60 (desktop: 98). Pages that score under 90 lose visitors before the first paint.

  • Reduce unused CSS

    750 ms · 112 KiB

    About 112 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 750 ms faster on a phone.

  • Improve image delivery

    450 ms · 206 KiB

    4 images could be 206 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.

  • 4 third-party services on the page

    4 third-party services load with your homepage (Google Tag Manager, Hotjar and cloudflare.com and others), adding 275 KiB and 300 ms of main-thread time.

  • 3 long tasks on the main thread

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

  • Font display

    50 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

  • Phones get a much slower page than desktops

    Desktop scores 98 but mobile only 60. A gap that wide usually means heavy scripts and images that hit phones hardest.

  • Use efficient cache lifetimes

    8 KiB

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

  • 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: 0.8 s

    A phone's processor spends 0.8 s on main-thread work while loading, 348 ms of it running JavaScript. That is comfortably low.

  • Server response: 3 ms

    3 ms

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

Core Web Vitals

4 to fix100
  • Largest Contentful Paint: 13.8 s

    13.8 s

    Your largest element takes 13.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “A Caucasian woman with dark hair, wearing a light blue shir…”.

  • Time to Interactive: 13.9 s

    13.9 s

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

  • First Contentful Paint: 4.2 s

    4.2 s

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

  • Speed Index: 5.9 s

    5.9 s

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

  • Tap response (INP) held steady for real visitors

    +1%

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

  • Largest content (LCP) held steady for real visitors

    +9%

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

7 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 0.9 s

    0.9 s

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 0.9 s

    0.9 s

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

  • Real-user TTFB: 429 ms

    429 ms

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

  • Total Blocking Time: 155 ms

    155 ms

    Scripts block the page for only 155 ms while loading. Good is under 200 ms.

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

100
  • 3 images below the first screen load straight away

    3 images further down the page (205 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 0.6 g of CO₂ per visit

    0.56 g

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

3 checks passed
  • Page weight: 2.0 MB in 61 requests

    2.0 MB

    Your homepage downloads 2.0 MB in 61 requests on a phone: other files 646 KiB (9), scripts 452 KiB (20) and images 329 KiB (14). That is a lean page.

  • 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

Google 100100
2 checks passed
  • Every image has alt text

    All 16 images in the HTML carry an alt attribute.

  • 43 automated accessibility rules passed

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

SEO

3 to fixGoogle 9280
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • Title is short (26 characters)

    Your title is only 26 characters: “Service Coordination, Inc.”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No social preview image

    No Open Graph image (also missing: og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 37 internal links, 6 external

    The homepage links to 37 pages on servicecoord.org and 6 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “We believe in the power of possibility.”.

  • Canonical URL set

    The canonical URL is https://www.servicecoord.org/.

  • Structured data in place

    Structured data found: Organization, 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://www.servicecoord.org/sitemap.xml.

AI search readiness

1 to fix88
  • Organization data is thin (2 of 6 facts)

    Your Organization JSON-LD is missing logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

  • No llms.txt

    There is no /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 (655 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix95
  • 15 pages without a meta description

    /services, /services/coordination-of-community-services, /services/supports-planning-services, /resources, /resources/glossary and /resources/faq and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 25 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.

  • Titles are unique

    Every page we checked has its own title.

  • 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

1 to fixGoogle 9693
  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “%c%d font-size:0;color:transparent NaN”.

2 checks passed
  • Tap targets are thumb-sized

    8 of 8 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix83
  • Thin social proof

    Social proof on the homepage: 4 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

  • 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 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 566 words of copy

    The homepage carries about 566 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Learn More About SCI”.

  • 7 calls to action

    The homepage has 7 calls to action, for example “Contact Us”, “Newsletter Signup” and “Learn More About SCI”.

  • 2 short forms

    2 short forms (4 fields at most) are right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Analytics and Hotjar.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Hotjar (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.

  • 4 cookies set on arrival

    4

    Opening the homepage sets 4 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.

  • 8 other companies contacted

    Loading the homepage contacts 8 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 servicecoord.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 | Hotjar

Company

Employees
1,084

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 18 issues on servicecoord.org, including 9 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

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