Website review, no card needed

lickslegal.com logo

lickslegal.com website review

Visit site (opens in a new tab)Reviewed 3 November 202640 issues · 84 checks

This review found 40 issues worth fixing on lickslegal.com, 13 of them high impact, across 84 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
3.2 s1.6 sMay 16Oct 312.6 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.8 s
May 23, 20261.9 s
May 30, 20262.2 s
Jun 6, 20262.3 s
Jun 13, 20262.5 s
Jun 20, 20262.6 s
Jun 27, 20262.6 s
Jul 4, 20262.5 s
Jul 11, 20262.6 s
Jul 18, 20262.3 s
Jul 25, 20262.4 s
Aug 1, 20262.4 s
Aug 8, 20262.4 s
Aug 15, 20262.5 s
Aug 22, 20262.4 s
Aug 29, 20262.4 s
Sep 5, 20262.5 s
Sep 12, 20262.5 s
Sep 19, 20262.6 s
Sep 26, 20262.8 s
Oct 3, 20262.9 s
Oct 10, 20263.0 s
Oct 17, 20263.1 s
Oct 24, 20262.7 s
Oct 31, 20262.6 s
Real-visitor tap response (INP)75th percentile, phones
97 ms69 msMay 16Oct 3174 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202683 ms
May 23, 202683 ms
May 30, 202684 ms
Jun 6, 202684 ms
Jun 13, 202681 ms
Jun 20, 202690 ms
Jun 27, 202694 ms
Jul 4, 202687 ms
Jul 11, 202686 ms
Jul 18, 202679 ms
Jul 25, 202673 ms
Aug 1, 202672 ms
Aug 8, 202675 ms
Aug 15, 202679 ms
Aug 22, 202678 ms
Aug 29, 202686 ms
Sep 5, 202689 ms
Sep 12, 202683 ms
Sep 19, 202685 ms
Sep 26, 202681 ms
Oct 3, 202678 ms
Oct 10, 202679 ms
Oct 17, 202679 ms
Oct 24, 202675 ms
Oct 31, 202674 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 lickslegal.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. lickslegal.com at 0.9 s0.9 s
  2. lickslegal.com at 1.7 s1.7 s
  3. lickslegal.com at 2.6 s2.6 s
  4. lickslegal.com at 3.4 s3.4 s
  5. lickslegal.com at 4.3 s4.3 s
  6. lickslegal.com at 5.1 s5.1 s
  7. lickslegal.com at 6.0 s6.0 s
  8. lickslegal.com at 6.9 s6.9 s

Speed

9 to fix50
  • Reduce unused JavaScript

    2.0 s · 391 KiB

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

  • Render-blocking requests

    1.5 s

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

  • Mobile performance score: 50

    50/100

    Your mobile performance score is 50. Pages that score under 90 lose visitors before the first paint.

  • 4 third-party services on the page

    4 third-party services load with your homepage (Google CDN, JSDelivr CDN and Other Google APIs/SDKs and others), adding 1.1 MB and 840 ms of main-thread time.

  • Improve image delivery

    450 ms · 436 KiB

    13 images could be 436 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.

  • Google CDN adds 656 ms

    656 ms

    Google CDN costs a phone 656 ms of main-thread work and 736 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 · 91 KiB

    About 91 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.

  • Main-thread work: 3.7 s

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

  • 1,549 HTML elements

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

  • 16 long tasks on the main thread

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

  • Font display

    50 ms

    Web 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.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

  • Minify CSS

    4 KiB

    4 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 122 ms

    122 ms

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

Core Web Vitals

6 to fix100
  • Time to Interactive: 22.5 s

    22.5 s

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

  • Largest Contentful Paint: 6.5 s

    6.5 s

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

  • Speed Index: 8.6 s

    8.6 s

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

  • Largest content (LCP) got 44% slower for real visitors

    +44%

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

  • Total Blocking Time: 563 ms

    563 ms

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

  • First Contentful Paint: 2.3 s

    2.3 s

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

7 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 1.7 s

    1.7 s

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

  • Real-user CLS: 0.03

    0.03

    For real visitors the layout shifts by 0.03 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.4 s

    1.4 s

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

  • Real-user TTFB: 755 ms

    755 ms

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

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

    -10%

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

  • Cumulative Layout Shift: 0.099

    0.099

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

Images and page weight

3 to fix53
  • Page weight: 11.4 MB in 66 requests

    11.4 MB

    Your homepage downloads 11.4 MB in 66 requests on a phone: media 6.9 MB (1), fonts 2.3 MB (8) and images 892 KiB (32). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    68fa9b76a475a66f48f0306d_Frases Pag Inicial - IN v8_4 - D.sv 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).

  • 3 images far larger than shown

    237 KiB

    3 images are downloaded at several times the size a phone draws them, for example homePractice28.jpg at 2,000 px wide, shown at 390 px. Resized copies would save about 237 KiB.

  • 5 images in older formats

    5 images (416 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 3.2 g of CO₂ per visit

    3.22 g

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

Accessibility

8 to fixGoogle 8488
  • Certain ARIA roles must be contained by particular parents (14 elements)

    Certain ARIA roles must be contained by particular parents: 14 elements on the page fail this check, rated critical by axe-core.

  • Certain ARIA roles must contain particular children (1 element)

    Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

  • 4 text elements with low contrast

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

  • Links look like plain text

    1 link inside paragraphs relies on colour alone to stand out.

  • 3 images without alt text

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

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

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

  • 4 form fields without a label

    4 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • Headings skip levels

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

1 checks passed
  • 47 automated accessibility rules passed

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

SEO

5 to fixGoogle 10071
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is long (129 characters)

    Your title is 129 characters, so Google will cut it off around 60: “Licks Attorneys - Brazilian leading law firm in complex litigation, regulation, IP prosec…”.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • Meta description is long (289 characters)

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

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 221 internal links, 12 external

    The homepage links to 221 pages on lickslegal.com and 12 external pages.

3 checks passed
  • Canonical URL set

    The canonical URL is https://www.lickslegal.com/.

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.lickslegal.com/sitemap.xml.

AI search readiness

1 to fix88
  • 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://www.lickslegal.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 (2,367 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix83
  • 1 linked page hidden from search

    https://www.lickslegal.com/publications/brazilian-patent-statistics-8A948141A13D7E1701A140FF6B9C5BE8-00 is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 15 pages without a meta description

    https://www.lickslegal.com/about-us, https://www.lickslegal.com/about-us/information-security-systems, https://www.lickslegal.com/about-us/about-licks-attorneys, https://www.lickslegal.com/about-us/av-capabilities, https://www.lickslegal.com/about-us/awards and https://www.lickslegal.com/about-us/covid-firm-policies and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages without an H1

    https://www.lickslegal.com/about-us and https://www.lickslegal.com/publications 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 186 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

1 to fixGoogle 9293
  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

2 checks passed
  • Tap targets are thumb-sized

    170 of 172 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix64
  • 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.

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

  • Thin social proof

    Social proof on the homepage: 1 testimonial or review block. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • No opening hours

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

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

  • 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 2,068 words of copy

    The homepage carries about 2,068 words of visible text.

3 checks passed
  • 3 calls to action

    The homepage has 3 calls to action, for example “Contact Us”, “Join Our Team” and “Subscribe”.

  • 4 short forms

    4 short forms (4 fields at most) are right on the homepage, asking for an email.

  • Phone number on the homepage

    Your phone number is on the homepage.

Privacy and tracking

  • 8 cookies set on arrival

    8

    Opening the homepage sets 8 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 lickslegal.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
LumisXP
Framework
Tailwind CSS
Hosting
Oracle Cloud

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 40 issues on lickslegal.com, including 15 speed issues, 5 SEO issues and 4 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
lickslegal.com website review: scores and fixes