Website review, no card needed
diakon.org website review
Visit site (opens in a new tab)Reviewed 2 November 202641 issues · 79 checks
This review found 41 issues worth fixing on diakon.org, 15 of them high impact, across 79 checks. The most urgent: use efficient cache lifetimes. 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
66DClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
Speed
Use efficient cache lifetimes
9.3 s · 10.1 MB45 files are served with short cache lifetimes, so returning visitors download them again (10.1 MB).
Render-blocking requests
10.6 s23 files block the first paint until they finish downloading. Deferring or inlining them could save about 10.6 s.
Mobile performance score: 40
40/100Your mobile performance score is 40. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Improve image delivery
2.0 MB15 images could be 2.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Google CDN and Adobe TypeKit and others), adding 1.2 MB and 515 ms of main-thread time.
Reduce unused JavaScript
310 ms · 265 KiBAbout 265 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 310 ms faster on a phone.
Google Tag Manager adds 478 ms
478 msGoogle Tag Manager costs a phone 478 ms of main-thread work and 514 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.
Reduce unused CSS
460 ms · 49 KiBAbout 49 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 460 ms faster on a phone.
5 long tasks on the main thread
5 long tasks block the main thread while loading, the longest for 367 ms. During a long task the page ignores taps.
Adobe TypeKit adds 10 ms
10 msAdobe TypeKit costs a phone 10 ms of main-thread work and 639 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
150 ms · 13 KiB13 KiB could be saved by minifying JavaScript.
Minify CSS
150 ms · 9 KiB9 KiB could be saved by minifying CSS.
Font display
100 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).
Legacy JavaScript
9 KiBPolyfills for old browsers add 9 KiB JavaScript that modern phones do not need.
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.4 s
A phone's processor spends 1.4 s on main-thread work while loading, 521 ms of it running JavaScript. That is comfortably low.
Server response: 2 ms
2 msYour server sent the HTML in 2 ms, well inside Google's 600 ms guideline.
Core Web Vitals
First Contentful Paint: 10.6 s
10.6 sThe first text or image appears after 10.6 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 10.6 s
10.6 sYour largest element takes 10.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Diakon empowers thousands of children, youth, families, and…”.
Time to Interactive: 19.6 s
19.6 sThe page becomes fully interactive after 19.6 s. Good is under 3.8 s.
Speed Index: 10.6 s
10.6 sVisually, the page fills in at 10.6 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 619 ms
619 msScripts block taps and scrolling for 619 ms in total while the page loads. Good is under 200 ms.
2 images without width and height
2 images have no width and height attributes, so the layout jumps as each one loads.
Not enough real-visitor data yet
Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.
1 checks passed
Cumulative Layout Shift: 0.042
0.042The layout barely moves while loading (CLS 0.042, good is under 0.1).
Images and page weight
Page weight: 11.3 MB in 75 requests
11.3 MBYour homepage downloads 11.3 MB in 75 requests on a phone: images 8.2 MB (23), scripts 2.2 MB (20) and fonts 820 KiB (16). Under 2 MB keeps phones on slow connections fast.
7 images over 500 KB
7 images weigh 7.1 MB together. On a phone connection a single image that size takes seconds.
19 images in older formats
19 images (8.2 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.
11 images below the first screen load straight away
11 images further down the page (1.5 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
2 images far larger than shown
378 KiB2 images are downloaded at several times the size a phone draws them, for example bhs-slider-26.jpg at 1,920 px wide, shown at 390 px. Resized copies would save about 378 KiB.
About 3.2 g of CO₂ per visit
3.21 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.21 g of CO₂e: 384.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Orphan list items
Some list items are not inside a list.
8 text elements with low contrast
8 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
7 images without alt text
7 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (3 elements)
All page content should be contained by landmarks: 3 elements on the page fail this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
ARIA role should be appropriate for the element (4 elements)
ARIA role should be appropriate for the element: 4 elements on the page fail this check, rated minor by axe-core.
1 checks passed
30 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 37 WCAG 2.2 A/AA and best-practice rules on the phone render: 30 passed and 7 failed. 1 more 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.
2 H1 headlines
There are 2 <h1> headlines (“Welcome to Diakon” and “News”). One clear main headline is easier for people and search engines.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
Meta description is long (373 characters)
Your meta description is 373 characters; Google truncates after about 160, so the end of your pitch is cut.
No social preview image
No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
No XML sitemap
No XML sitemap at https://diakon.org/sitemap.xml, so Google discovers your pages only by following links.
No robots.txt
There is no robots.txt at diakon.org/robots.txt, the first file search crawlers ask for.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
79 internal links, 8 external
The homepage links to 79 pages on diakon.org and 8 external pages.
1 checks passed
Title: 62 characters
Your title is a healthy 62 characters: “Diakon - Children, Youth, & Family Services - Housing Services”.
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://diakon.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.
2 checks passed
AI answer engines may read the site
There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.
Text is in the HTML
Your server sends the page's text in the HTML (470 words), so crawlers that don't run JavaScript still read it.
Other pages
1 page without a meta description
https://diakon.org/giving/online-donation has 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 52 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
3 small tap targets
3 of 10 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
Missing source maps
Large scripts ship without source maps.
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.
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 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 316 words of copy
The homepage carries about 316 words of visible text.
3 checks passed
4 calls to action
The homepage has 4 calls to action, for example “Contact Us”, “Sign Up For Newsletter” and “Contact”.
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
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (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.
5 cookies set on arrival
5Opening the homepage sets 5 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.
12 other companies contacted
Loading the homepage contacts 12 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 diakon.org, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- jQuery
- Analytics
- Google Tag Manager
- Hosting
- DigitalOcean
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 41 issues on diakon.org, including 16 speed issues, 7 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.