Website review, no card needed
medanswering.com website review
Visit site (opens in a new tab)Reviewed 27 October 202631 issues · 74 checks
This review found 31 issues worth fixing on medanswering.com, 11 of them high impact, across 74 checks. The most urgent: render-blocking requests. 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
1.0 s
1.9 s
2.9 s
3.9 s
4.9 s
5.8 s
6.8 s
7.8 s
Speed
Render-blocking requests
3.4 s11 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.4 s.
Reduce unused CSS
860 ms · 164 KiBAbout 164 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 860 ms faster on a phone.
Mobile performance score: 50
50/100Your mobile performance score is 50 (desktop: 68). Pages that score under 90 lose visitors before the first paint.
Improve image delivery
650 ms · 113 KiB2 images could be 113 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 650 ms faster on a phone.
2 long tasks on the main thread
2 long tasks block the main thread while loading, the longest for 464 ms. During a long task the page ignores taps.
Reduce unused JavaScript
300 ms · 43 KiBAbout 43 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.
Adobe TypeKit adds 0 ms
0 msAdobe TypeKit costs a phone 0 ms of main-thread work and 383 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.
Use efficient cache lifetimes
150 ms · 6 KiB2 files are served with short cache lifetimes, so returning visitors download them again (6 KiB).
3 third-party services on the page
3 third-party services load with your homepage (FontAwesome CDN, Adobe TypeKit and Google Fonts), adding 670 KiB and 54 ms of main-thread time.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 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.
2 checks passed
Main-thread work: 2.0 s
A phone's processor spends 2.0 s on main-thread work while loading, 302 ms of it running JavaScript. That is comfortably low.
Server response: 30 ms
30 msYour server sent the HTML in 30 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 7.4 s
7.4 sYour largest element takes 7.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “MAS Connects Medicaid enrollees to health care through non-…”. Most of its time is element render delay (5.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.
First Contentful Paint: 5.1 s
5.1 sThe first text or image appears after 5.1 s on a phone. Good is under 1.8 s.
Time to Interactive: 7.9 s
7.9 sThe page becomes fully interactive after 7.9 s. Good is under 3.8 s.
Cumulative Layout Shift: 0.166
0.166The layout shifts by 0.166 while loading, so content jumps under the reader's thumb. Good is under 0.1.
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
Total Blocking Time: 4 ms
4 msScripts block the page for only 4 ms while loading. Good is under 200 ms.
Images and page weight
1 image in older formats
1 image (93 KiB) is 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 0.4 g of CO₂ per visit
0.42 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.42 g of CO₂e: 50.4 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: 1.5 MB in 59 requests
1.5 MBYour homepage downloads 1.5 MB in 59 requests on a phone: fonts 691 KiB (20), images 489 KiB (11) and scripts 138 KiB (13). That is a lean page.
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
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
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.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 5 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 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 4 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Page is set to noindex
The robots meta tag says “noindex, nofollow”: Google is told not to list this page at all.
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
Blocked from indexing
Google's crawler is blocked from indexing this page.
Title is short (29 characters)
Your title is only 29 characters: “MAS | A Driving Force in NEMT”. Between 30 and 65 characters leaves room to say what you do and for whom.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
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://wp2.medanswering.com/sitemap.xml, so Google discovers your pages only by following links.
9 links with vague text
9 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
61 internal links, 15 external
The homepage links to 61 pages on medanswering.com and 15 external pages.
3 checks passed
One H1 headline
Your main headline reads: “Medicaid Transportation”.
Canonical URL set
The canonical URL is https://wp2.medanswering.com/.
robots.txt in place
robots.txt is in place.
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://wp2.medanswering.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.
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 (730 words), so crawlers that don't run JavaScript still read it.
Other pages
15 linked pages hidden from search
https://wp2.medanswering.com/about-mas, https://wp2.medanswering.com/about-mas/leadership-team, https://wp2.medanswering.com/about-mas/commitment-to-enrollees, https://wp2.medanswering.com/about-mas/contact-us, https://wp2.medanswering.com/contact-center and https://wp2.medanswering.com/transportation-provider-relations-team and 9 others are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.
15 pages without a meta description
https://wp2.medanswering.com/about-mas, https://wp2.medanswering.com/about-mas/leadership-team, https://wp2.medanswering.com/about-mas/commitment-to-enrollees, https://wp2.medanswering.com/about-mas/contact-us, https://wp2.medanswering.com/contact-center and https://wp2.medanswering.com/transportation-provider-relations-team and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.
1 page slow to respond
https://wp2.medanswering.com/medical-provider-relations-team took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 31 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.
Every page has an H1
Each page we checked has a main headline.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
3 small tap targets
3 of 15 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Browser-reported issues
Chrome logged issues while loading the page (“Mixed content”).
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 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 579 words of copy
The homepage carries about 579 words of visible text.
3 checks passed
17 calls to action
The homepage has 17 calls to action, for example “Contact Us”, “Contact Center” and “Learn More”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Analytics.
Privacy and tracking
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.
5 other companies contacted
Loading the homepage contacts 5 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 medanswering.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Hosting
- Datacate
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 31 issues on medanswering.com, including 12 speed issues, 9 SEO issues and 3 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.