Website review, no card needed
chilmarkresearch.com website review
Visit site (opens in a new tab)Reviewed 22 November 202644 issues · 91 checks
This review found 44 issues worth fixing on chilmarkresearch.com, 15 of them high impact, across 91 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
How it loaded on a phone
0.9 s
1.9 s
2.8 s
3.8 s
4.7 s
5.6 s
6.6 s
7.5 s
Speed
Use efficient cache lifetimes
4.3 s · 2.5 MB488 files are served with short cache lifetimes, so returning visitors download them again (2.5 MB).
Reduce unused JavaScript
5.1 s · 924 KiBAbout 924 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
2.1 s18 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.1 s.
10,503 HTML elements
The page has 10,503 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Improve image delivery
700 ms · 1.3 MB23 images could be 1.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 700 ms faster on a phone.
Mobile performance score: 58
58/100Your mobile performance score is 58. Pages that score under 90 lose visitors before the first paint.
Minify JavaScript
600 ms · 86 KiB86 KiB could be saved by minifying JavaScript.
Reduce unused CSS
600 ms · 85 KiBAbout 85 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.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Facebook and Google Fonts and others), adding 2.5 MB and 181 ms of main-thread time.
Main-thread work: 2.5 s
A phone's processor spends 2.5 s on main-thread work while loading, 483 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
sportpulseapiz.com adds 0 ms
0 mssportpulseapiz.com costs a phone 0 ms of main-thread work and 1.6 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 Fonts adds 5 ms
5 msGoogle Fonts costs a phone 5 ms of main-thread work and 494 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
150 ms · 20 KiBPolyfills for old browsers add 20 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
8 long tasks on the main thread
8 long tasks block the main thread while loading, the longest for 160 ms. During a long task the page ignores taps.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Minify CSS
7 KiB7 KiB could be saved by minifying CSS.
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.
1 checks passed
Server response: 21 ms
21 msYour server sent the HTML in 21 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.
Largest Contentful Paint: 24.8 s
24.8 sYour largest element takes 24.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 25.7 s
25.7 sThe page becomes fully interactive after 25.7 s. Good is under 3.8 s.
First Contentful Paint: 3.3 s
3.3 sThe first text or image appears after 3.3 s on a phone. Good is under 1.8 s.
Real-user LCP: 2.7 s
2.7 sReal visitors wait 2.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.12
0.12For real visitors the layout shifts by 0.12 (75th percentile). Good is under 0.1.
Speed Index: 5.6 s
5.6 sVisually, the page fills in at 5.6 s (Speed Index). Good is under 3.4 s.
23 images without width and height
23 images have no width and height attributes, so the layout jumps as each one loads.
Cumulative Layout Shift: 0.124
0.124The layout shifts by 0.124 while loading, so content jumps under the reader's thumb. Good is under 0.1.
4 checks passed
Real-user INP: 119 ms
119 msReal visitors wait 119 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 1.3 s
1.3 sReal visitors see the first content after 1.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 651 ms
651 msReal visitors wait 651 ms for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 162 ms
162 msScripts block the page for only 162 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 6.3 MB in 555 requests
6.3 MBYour homepage downloads 6.3 MB in 555 requests on a phone: images 4.0 MB (475), scripts 1.3 MB (21) and fonts 655 KiB (29). Under 2 MB keeps phones on slow connections fast.
2 images in older formats
2 images (490 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.
About 1.8 g of CO₂ per visit
1.79 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.79 g of CO₂e: 215.1 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
17 text elements with low contrast
17 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
205 images without alt text
205 images have no alt text, which hurts accessibility and image search.
Scrollable region must have keyboard access (1 element)
Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.
All page content should be contained by landmarks (202 elements)
All page content should be contained by landmarks: 202 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
18 links without text
18 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 (25 elements)
Alternative text of images should not be repeated as text: 25 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h1 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.
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
41 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: 41 passed and 9 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Structured data has 1 problem
Structured data found (FAQPage, Organization, Person and WebSite) but with 1 problem, for example “ld+json block 5 is not valid JSON (Unexpected non-whitespace character after JSON at position 2)”.
195 internal links, 105 external
The homepage links to 195 pages on chilmarkresearch.com and 105 external pages.
7 checks passed
Meta description: 139 characters
Your meta description is 139 characters: “Xoilac TV - Link trực tiếp bóng đá bình luận Tiếng Việt. Truy cập Xoilacz.ca xem lịch thi đấu, kết quả bóng đá, tỷ số t…”.
One H1 headline
Your main headline reads: “XoilacZ - Xem Trực tiếp XoilacTV HD - Link Xoilac TV mới nhất hôm nay”.
Title: 59 characters
Your title is a healthy 59 characters: “XoilacZ - Xem trực tiếp bóng đá HD - Link Xoilac TV Hôm nay”.
Canonical URL set
The canonical URL is https://savethislife.com/.
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://savethislife.com/sitemap.xml.
AI search readiness
No llms.txt
There is no https://savethislife.com/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: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
Text is in the HTML
Your server sends the page's text in the HTML (6,003 words), so crawlers that don't run JavaScript still read it.
Other pages
1 linked page hidden from search
https://savethislife.com/video is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
2 pages without a meta description
https://savethislife.com/video and https://savethislife.com/danh-sach-giai-dau have no meta description, so Google writes the search snippet from whatever text it finds.
4 pages without an H1
https://savethislife.com/cam-nang, https://savethislife.com/top-nha-cai, https://savethislife.com/tin-tuc-moi-nhat and https://savethislife.com/soi-keo 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 147 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.
Titles are unique
Every page we checked has its own title.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
10 broken images
10 images failed to load on a phone, for example https://imgts.sportpulseapiz.com/football/competition/4zp5rzghp5q82w1/image/small.
33 distorted images
33 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
2 low-resolution images
2 images are served at too low a resolution for sharp phone screens.
Missing source maps
Large scripts ship without source maps.
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
55 of 56 tappable elements near the top are at least 24 px.
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 calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
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 phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
Thin social proof
Social proof on the homepage: 3 trust badges. 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 opening hours
The homepage shows no opening hours. If customers visit or call, show when.
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 3,765 words of copy
The homepage carries about 3,765 words of visible text.
1 checks passed
Analytics in place
Analytics detected: Google Analytics.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads 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.
2 cookies set on arrival
2Opening the homepage sets 2 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 chilmarkresearch.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
- The footer still says © 2020.
Stack
- CMS
- WordPress
- Framework
- Vue.js
- Analytics
- Google Analytics
- Hosting
- Cloudflare
Company
- Headquarters
- Boston
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 44 issues on chilmarkresearch.com, including 21 speed issues, 1 SEO issue and 6 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.