Website review, no card needed
inchcape.lt website review
Visit site (opens in a new tab)Reviewed 1 November 202646 issues · 88 checks
This review found 46 issues worth fixing on inchcape.lt, 23 of them high impact, across 88 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
68DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 1.8 s |
| May 16, 2026 | 1.8 s |
| May 23, 2026 | 1.8 s |
| May 30, 2026 | 1.7 s |
| Jun 6, 2026 | 1.7 s |
| Jun 13, 2026 | 1.7 s |
| Jun 20, 2026 | 1.7 s |
| Jun 27, 2026 | 1.8 s |
| Jul 4, 2026 | 1.8 s |
| Jul 11, 2026 | 1.8 s |
| Jul 18, 2026 | 1.8 s |
| Jul 25, 2026 | 1.8 s |
| Aug 1, 2026 | 1.9 s |
| Aug 8, 2026 | 1.9 s |
| Aug 15, 2026 | 1.8 s |
| Aug 22, 2026 | 1.7 s |
| Aug 29, 2026 | 1.5 s |
| Sep 5, 2026 | 1.4 s |
| Sep 12, 2026 | 1.4 s |
| Sep 19, 2026 | 1.4 s |
| Sep 26, 2026 | 1.4 s |
| Oct 3, 2026 | 1.5 s |
| Oct 10, 2026 | 1.5 s |
| Oct 17, 2026 | 1.5 s |
| Oct 24, 2026 | 1.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 96 ms |
| May 16, 2026 | 95 ms |
| May 23, 2026 | 94 ms |
| May 30, 2026 | 91 ms |
| Jun 6, 2026 | 90 ms |
| Jun 13, 2026 | 92 ms |
| Jun 20, 2026 | 95 ms |
| Jun 27, 2026 | 97 ms |
| Jul 4, 2026 | 96 ms |
| Jul 11, 2026 | 94 ms |
| Jul 18, 2026 | 94 ms |
| Jul 25, 2026 | 96 ms |
| Aug 1, 2026 | 100 ms |
| Aug 8, 2026 | 100 ms |
| Aug 15, 2026 | 97 ms |
| Aug 22, 2026 | 95 ms |
| Aug 29, 2026 | 93 ms |
| Sep 5, 2026 | 94 ms |
| Sep 12, 2026 | 95 ms |
| Sep 19, 2026 | 97 ms |
| Sep 26, 2026 | 98 ms |
| Oct 3, 2026 | 96 ms |
| Oct 10, 2026 | 96 ms |
| Oct 17, 2026 | 95 ms |
| Oct 24, 2026 | 95 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
How it loaded on a phone
0.5 s
1.0 s
1.5 s
2.1 s
2.6 s
3.1 s
3.6 s
4.1 s
Speed
Use efficient cache lifetimes
16.4 s · 13.4 MB73 files are served with short cache lifetimes, so returning visitors download them again (13.4 MB).
Improve image delivery
14.2 s · 11.7 MB12 images could be 11.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 14.2 s faster on a phone.
Reduce unused JavaScript
6.6 s · 860 KiBAbout 860 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 6.6 s faster on a phone.
Render-blocking requests
3.8 s16 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.8 s.
Reduce unused CSS
1.2 s · 294 KiBAbout 294 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.2 s faster on a phone.
Font display
1.1 sWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 1.1 s).
Mobile performance score: 26
26/100Your mobile performance score is 26. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Google CDN and Facebook and others), adding 1.9 MB and 1.7 s of main-thread time.
Google Tag Manager adds 675 ms
675 msGoogle Tag Manager costs a phone 675 ms of main-thread work and 658 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 CDN adds 602 ms
602 msGoogle CDN costs a phone 602 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.
Main-thread work: 3.9 s
A phone's processor spends 3.9 s on main-thread work while loading, 2.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
16 long tasks on the main thread
16 long tasks block the main thread while loading, the longest for 264 ms. During a long task the page ignores taps.
Duplicated JavaScript
57 KiB57 KiB JavaScript is shipped twice across bundles.
Document request latency
41 KiBThe HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.
Legacy JavaScript
21 KiBPolyfills for old browsers add 21 KiB JavaScript that modern phones do not need.
Minify CSS
4 KiB4 KiB could be saved by minifying CSS.
Minify JavaScript
3 KiB3 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 219 ms
219 msYour server sent the HTML in 219 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: 73.0 s
73.0 sYour largest element takes 73.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “FORD”.
Time to Interactive: 77.0 s
77.0 sThe page becomes fully interactive after 77.0 s. Good is under 3.8 s.
Speed Index: 12.9 s
12.9 sVisually, the page fills in at 12.9 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 948 ms
948 msScripts block taps and scrolling for 948 ms in total while the page loads. Good is under 200 ms.
Cumulative Layout Shift: 0.341
0.341The layout shifts by 0.341 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Real-user CLS: 0.12
0.12For real visitors the layout shifts by 0.12 (75th percentile). Good is under 0.1.
49 images without width and height
49 images have no width and height attributes, so the layout jumps as each one loads.
First Contentful Paint: 2.0 s
2.0 sThe first text or image appears after 2.0 s on a phone. Good is under 1.8 s.
Tap response (INP) held steady for real visitors
-1%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 96 ms to 95 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user LCP: 1.9 s
1.9 sReal visitors wait 1.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 95 ms
95 msReal visitors wait 95 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 1.1 s
1.1 sReal visitors see the first content after 1.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 561 ms
561 msReal visitors wait 561 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 15% faster for real visitors
-15%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 1.8 s to 1.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
Page weight: 21.9 MB in 113 requests
21.9 MBYour homepage downloads 21.9 MB in 113 requests on a phone: images 18.7 MB (44), scripts 2.1 MB (28) and other files 366 KiB (16). Under 2 MB keeps phones on slow connections fast.
12 images over 500 KB
12 images weigh 13.6 MB together. On a phone connection a single image that size takes seconds.
5 images far larger than shown
1.3 MB5 images are downloaded at several times the size a phone draws them, for example mazda-dienos-1200x1200-empty-kaunas-day.png at 1,200 px wide, shown at 366 px. Resized copies would save about 1.3 MB.
21 images in older formats
21 images (14.7 MB) 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 6.2 g of CO₂ per visit
6.20 gBy the Sustainable Web Design model, a visit to your homepage emits about 6.20 g of CO₂e: 743.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
14 tap targets too small
14 tap targets are too small or too close together to hit reliably with a finger.
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.
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
17 images without alt text
17 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (10 elements)
All page content should be contained by landmarks: 10 elements on the page fail this check, rated moderate by axe-core.
35 links without text
35 visible links have no text or label, so screen readers cannot say where they go.
3 form fields without a label
3 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h1 → h3, h1 → h3 and h1 → h3), which makes the page harder to scan with a screen reader.
1 checks passed
46 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: 46 passed and 8 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
16 H1 headlines
There are 16 <h1> headlines (“FORD”, “JAGUAR” and “LAND ROVER”). One clear main headline is easier for people and search engines.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
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 X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
28 internal links, 33 external
The homepage links to 28 pages on inchcape.lt and 33 external pages.
3 checks passed
Title: 32 characters
Your title is a healthy 32 characters: “Inchcape Lithuania - Pagrindinis”.
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://inchcape.lt/sitemap.xml.
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://www.inchcape.lt/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 (623 words), so crawlers that don't run JavaScript still read it.
Other pages
12 pages without a meta description
https://www.inchcape.lt/apie-mus, https://www.inchcape.lt/pasiulymai, https://www.inchcape.lt/servisas, https://www.inchcape.lt/draudimas-ir-finansavimas, https://www.inchcape.lt/bandomasis-vaziavimas and https://www.inchcape.lt/kontaktai and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages slow to respond
https://www.inchcape.lt/bandomasis-vaziavimas and https://www.inchcape.lt/kontaktai took over 3 s to send their HTML from our server.
12 internal pages checked
We fetched 12 pages linked from your homepage and read each the way a search engine does.
6 checks passed
Linked pages load
All 12 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.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 12 pages that loaded have a <title>.
Best practices
18 small tap targets
18 of 60 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
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
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.
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 direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
Only about 190 words
The homepage has only about 190 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
2 checks passed
1 short form
A short form (2 fields at most) is right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Meta Pixel (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.
8 cookies set on arrival
8Opening the homepage sets 8 cookies (measured from a US location before any click).
22 other companies contacted
Loading the homepage contacts 22 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Cookiebot
A consent management tool (Cookiebot) 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 inchcape.lt, 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 © 2023.
Stack
- Framework
- jQuery
- Analytics
- Google Tag Manager
- Hosting
- AWS
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 46 issues on inchcape.lt, including 21 speed issues, 5 SEO issues and 5 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.