Website review, no card needed

lexolution.net logo

lexolution.net website review

Visit site (opens in a new tab)Reviewed 24 October 202628 issues · 80 checks

This review found 28 issues worth fixing on lexolution.net, 7 of them high impact, across 80 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
3.5 s2.7 sMay 2Oct 173.2 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20263.4 s
May 9, 20263.3 s
May 16, 20263.2 s
May 23, 20263.1 s
May 30, 20263.0 s
Jun 6, 20262.8 s
Jun 13, 20262.9 s
Jun 20, 20262.9 s
Jun 27, 20263.1 s
Jul 4, 20263.2 s
Jul 11, 20263.2 s
Jul 18, 20263.2 s
Jul 25, 20263.1 s
Aug 1, 20263.0 s
Aug 8, 20263.0 s
Aug 15, 20263.0 s
Aug 22, 20263.0 s
Aug 29, 20262.9 s
Sep 5, 20262.9 s
Sep 12, 20262.9 s
Sep 19, 20262.9 s
Sep 26, 20263.0 s
Oct 3, 20263.1 s
Oct 10, 20263.1 s
Oct 17, 20263.2 s
Real-visitor tap response (INP)75th percentile, phones
191 ms139 msMay 2Oct 17148 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026170 ms
May 9, 2026171 ms
May 16, 2026172 ms
May 23, 2026185 ms
May 30, 2026179 ms
Jun 6, 2026167 ms
Jun 13, 2026161 ms
Jun 20, 2026145 ms
Jun 27, 2026148 ms
Jul 4, 2026151 ms
Jul 11, 2026151 ms
Jul 18, 2026156 ms
Jul 25, 2026160 ms
Aug 1, 2026167 ms
Aug 8, 2026169 ms
Aug 15, 2026168 ms
Aug 22, 2026164 ms
Aug 29, 2026155 ms
Sep 5, 2026152 ms
Sep 12, 2026149 ms
Sep 19, 2026146 ms
Sep 26, 2026150 ms
Oct 3, 2026153 ms
Oct 10, 2026145 ms
Oct 17, 2026148 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 lexolution.net (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

9 to fix56
  • Render-blocking requests

    3.1 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, osano.com and website-files.com and others), adding 1.6 MB and 1.0 s of main-thread time.

  • Mobile performance score: 56

    56/100

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

  • Reduce unused JavaScript

    150 ms · 444 KiB

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

  • Google Tag Manager adds 455 ms

    455 ms

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

  • 8 long tasks on the main thread

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

  • Main-thread work: 2.2 s

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

  • website-files.com adds 111 ms

    111 ms

    website-files.com costs a phone 111 ms of main-thread work and 588 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.

  • 1,518 HTML elements

    The page has 1,518 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Reduce unused CSS

    150 ms · 44 KiB

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

  • Use efficient cache lifetimes

    150 ms · 31 KiB

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

  • Improve image delivery

    19 KiB

    1 image could be 19 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Phones get a much slower page than desktops

    Desktop scores 83 but mobile only 56. 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.

1 checks passed
  • Server response: 3 ms

    3 ms

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

Core Web Vitals

7 to fix100
  • 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.

  • Time to Interactive: 13.4 s

    13.4 s

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

  • Largest Contentful Paint: 5.4 s

    5.4 s

    Your largest element takes 5.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • First Contentful Paint: 3.8 s

    3.8 s

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

  • Real-user FCP: 1.9 s

    1.9 s

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

  • Total Blocking Time: 581 ms

    581 ms

    Scripts block taps and scrolling for 581 ms in total while the page loads. Good is under 200 ms.

  • Speed Index: 4.0 s

    4.0 s

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

  • Largest content (LCP) held steady for real visitors

    -7%

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

6 checks passed
  • Real-user LCP: 2.1 s

    2.1 s

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

  • Real-user INP: 150 ms

    150 ms

    Real visitors wait 150 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • 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 TTFB: 517 ms

    517 ms

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

  • Tap response (INP) got 14% faster for real visitors

    -14%

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

  • 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 fix97
  • An image on the first screen is lazy-loaded

    67222ed00ec3fcaad78e369e_Careers Hero-p-500.avif is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • About 0.5 g of CO₂ per visit

    0.48 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.48 g of CO₂e: 57.5 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.7 MB in 73 requests

    1.7 MB

    Your homepage downloads 1.7 MB in 73 requests on a phone: scripts 1.1 MB (31), fonts 262 KiB (5) and images 218 KiB (15). 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

2 to fixGoogle 9797
  • 19 text elements with low contrast

    19 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • All page content should be contained by landmarks (30 elements)

    All page content should be contained by landmarks: 30 elements on the page fail this check, rated moderate by axe-core.

2 checks passed
  • Every image has alt text

    All 34 images in the HTML carry an alt attribute.

  • 42 automated accessibility rules passed

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

SEO

2 to fixGoogle 9294
  • Structured data has 1 problem

    Structured data found (LegalService, Organization and WebPage) but with 1 problem, for example “WebPage: url is not an absolute URL ("https://www.consilio.com/about-consilio/careers")”.

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • 137 internal links, 10 external

    The homepage links to 137 pages on lexolution.net and 10 external pages.

7 checks passed
  • Meta description: 103 characters

    Your meta description is 103 characters: “Discover job opportunities and find your legal career path at Consilio. See open positions at Consilio.”.

  • One H1 headline

    Your main headline reads: “At Consilio, your voice matters.”.

  • Title: 62 characters

    Your title is a healthy 62 characters: “Careers | eDiscovery and legal technology solutions | Consilio”.

  • Canonical URL set

    The canonical URL is https://www.consilio.com/about-consilio/careers.

  • 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://www.consilio.com/sitemap.xml.

AI search readiness

100
4 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 name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://www.consilio.com/llms.txt (8 KiB, 55 links), a plain-text guide to the site for AI tools.

Other pages

3 to fix86
  • 10 pages share 2 titles

    https://www.consilio.com/about-consilio/careers, https://www.consilio.com/en-gb/about-consilio/careers, https://www.consilio.com/zh-cn/about-consilio/careers, https://www.consilio.com/en-au/about-consilio/careers, https://www.consilio.com/fr/about-consilio/careers and https://www.consilio.com/de/about-consilio/careers and 1 other all use the title “Careers | eDiscovery and legal technology solutions | Consilio”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

  • 9 pages share a meta description

    https://www.consilio.com/en-gb/about-consilio/careers, https://www.consilio.com/zh-cn/about-consilio/careers, https://www.consilio.com/en-au/about-consilio/careers, https://www.consilio.com/fr/about-consilio/careers, https://www.consilio.com/de/about-consilio/careers and https://www.consilio.com/en-ca/about-consilio/careers use the same meta description. A description written for each page earns more clicks.

  • 2 links to non-canonical URLs

    Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://www.consilio.com/ja/about-consilio/careers, whose canonical is https://www.consilio.com/ja. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 15 internal pages checked

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

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • 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

2 to fixGoogle 9687
  • 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.

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “gsap is not defined”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix81
  • 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: 1 customer or partner logo. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

    The homepage carries about 848 words of visible text.

6 checks passed
  • 4 calls to action

    The homepage has 4 calls to action, for example “Contact Us” and “Learn More”.

  • 2 short forms

    2 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics, Hotjar and LinkedIn Insight.

  • Direct contact links

    Visitors can reach you directly: 7 phone links and 7 email links.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

Privacy and tracking

  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads Google Tag Manager (measured from a US location before any click). A consent tool (Osano) is installed; check it blocks these until visitors agree where the law requires it.

  • 1 cookie set on arrival

    1

    Opening the homepage sets 1 cookie (measured from a US location before any click).

  • 9 other companies contacted

    Loading the homepage contacts 9 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • Consent tool: Osano

    A consent management tool (Osano) loads with the page.

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 lexolution.net, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
Webflow
Analytics
Google Analytics | Google Tag Manager | Hotjar

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 28 issues on lexolution.net, including 16 speed issues, 2 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