Website review, no card needed

inline.group logo

inline.group website review

Visit site (opens in a new tab)Reviewed 22 October 202635 issues · 75 checks

This review found 35 issues worth fixing on inline.group, 13 of them high impact, across 75 checks. The most urgent: reduce unused JavaScript. 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
1.6 s1.2 sMay 16Aug 11.4 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.3 s
May 23, 20261.4 s
May 30, 20261.6 s
Aug 1, 20261.4 s

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 inline.group (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

9 to fix36
  • Reduce unused JavaScript

    2.5 s · 925 KiB

    About 925 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.5 s faster on a phone.

  • Render-blocking requests

    1.1 s

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

  • Mobile performance score: 36

    36/100

    Your mobile performance score is 36 (desktop: 65). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Main-thread work: 4.6 s

    A phone's processor spends 4.6 s on main-thread work while loading, 2.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • 8 third-party services on the page

    8 third-party services load with your homepage (YouTube, Google Tag Manager and Facebook and others), adding 1.8 MB and 1.6 s of main-thread time.

  • YouTube adds 658 ms

    658 ms

    YouTube costs a phone 658 ms of main-thread work and 963 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 Tag Manager adds 558 ms

    558 ms

    Google Tag Manager costs a phone 558 ms of main-thread work and 501 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

    300 ms · 143 KiB

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

  • 20 long tasks on the main thread

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

  • Use efficient cache lifetimes

    242 KiB

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

  • Legacy JavaScript

    12 KiB

    Polyfills for old browsers add 12 KiB JavaScript that modern phones do not need.

  • Phones get a much slower page than desktops

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

  • 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: 64 ms

    64 ms

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

Core Web Vitals

6 to fix43
  • First Contentful Paint: 7.9 s

    7.9 s

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

  • Largest Contentful Paint: 8.5 s

    8.5 s

    Your largest element takes 8.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “APPs. Physicians. Dentists. Behavioral Health Providers. In…”.

  • Time to Interactive: 19.1 s

    19.1 s

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

  • Speed Index: 7.9 s

    7.9 s

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

  • Total Blocking Time: 1.0 s

    1.0 s

    Scripts block taps and scrolling for 1.0 s 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.

  • Largest content (LCP) held steady for real visitors

    +9%

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

  • 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.001

    0.001

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

Images and page weight

1 to fix85
  • Page weight: 2.7 MB in 77 requests

    2.7 MB

    Your homepage downloads 2.7 MB in 77 requests on a phone: scripts 1.9 MB (30), other files 498 KiB (19) and fonts 116 KiB (6). Under 2 MB keeps phones on slow connections fast.

  • About 0.8 g of CO₂ per visit

    0.78 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • 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

4 to fixGoogle 8793
  • Links must have discernible text (4 elements)

    Links must have discernible text: 4 elements on the page fail this check, rated serious by axe-core.

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • 20 images without alt text

    20 images have no alt text, which hurts accessibility and image search.

  • ARIA role should be appropriate for the element (7 elements)

    ARIA role should be appropriate for the element: 7 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

    Headings skip levels (h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.

1 checks passed
  • 44 automated accessibility rules passed

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

SEO

6 to fixGoogle 9273
  • Title is long (67 characters)

    Your title is 67 characters, so Google will cut it off around 60: “The Inline Group | Physician recruitment without the placement fees”.

  • 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 (474 characters)

    Your meta description is 474 characters; Google truncates after about 160, so the end of your pitch is cut.

  • Structured data has 1 problem

    Structured data found (Organization and WebSite) but with 1 problem, for example “Organization: missing name”.

  • 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://www.inline.group/sitemap.xml, so Google discovers your pages only by following links.

  • 19 internal links, 17 external

    The homepage links to 19 pages on inline.group and 17 external pages.

2 checks passed
  • One H1 headline

    Your main headline reads: “A Better Way to Reach Healthcare Providers”.

  • robots.txt in place

    robots.txt is in place.

AI search readiness

100
  • No llms.txt

    There is no https://www.inline.group/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 url, logo, sameAs (social profiles) and contact details; name and description would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (832 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix86
  • 9 pages share a title

    /, https://www.inline.group/contact-us, https://www.inline.group/platform-options, https://www.inline.group/process, https://www.inline.group/candidates and https://www.inline.group/case-studies and 3 others all use the title “The Inline Group | Physician recruitment without the placement fees”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 10 pages share a meta description

    https://www.inline.group/contact-us, https://www.inline.group/platform-options, https://www.inline.group/process, https://www.inline.group/candidates, https://www.inline.group/case-studies and https://www.inline.group/about and 4 others use the same meta description. A description written for each page earns more clicks.

  • 1 page without an H1

    https://www.inline.group/contact-us has no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://www.inline.group/schedule has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 10 internal pages checked

    We fetched 10 pages linked from your homepage and read each the way a search engine does.

5 checks passed
  • Linked pages load

    All 10 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 10 pages that loaded have a meta description.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 10 pages that loaded have a <title>.

Best practices

2 to fixGoogle 7393
  • 5 third-party cookies

    5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • 4 distorted images

    4 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

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

3 to fix67
  • 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.

  • Thin social proof

    Social proof on the homepage: 26 testimonial or review blocks. 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 520 words of copy

    The homepage carries about 520 words of visible text.

3 checks passed
  • 8 calls to action

    The homepage has 8 calls to action, for example “Contact”, “Join Our Team” and “Get a quote”.

  • 1 short form

    A short form (0 fields at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Analytics.

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

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

  • 12 cookies set on arrival

    12

    Opening the homepage sets 12 cookies, 1 of them by other companies (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.

  • 25 other companies contacted

    Loading the homepage contacts 25 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 inline.group, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
Nuxt
Analytics
Google Analytics
Hosting
Netlify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 35 issues on inline.group, including 15 speed issues, 6 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

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