Website review, no card needed
litexpo.lt website review
Visit site (opens in a new tab)Reviewed 22 October 202630 issues · 74 checks
This review found 30 issues worth fixing on litexpo.lt, 12 of them high impact, across 74 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
80BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 873 ms |
| May 9, 2026 | 845 ms |
| May 16, 2026 | 815 ms |
| May 23, 2026 | 837 ms |
| May 30, 2026 | 866 ms |
| Jun 6, 2026 | 916 ms |
| Jun 13, 2026 | 1.0 s |
| Jun 20, 2026 | 1.1 s |
| Jun 27, 2026 | 1.2 s |
| Jul 4, 2026 | 1.2 s |
| Jul 11, 2026 | 1.2 s |
| Jul 18, 2026 | 1.3 s |
| Jul 25, 2026 | 1.2 s |
| Aug 1, 2026 | 1.2 s |
| Aug 8, 2026 | 1.2 s |
| Aug 15, 2026 | 1.2 s |
| Aug 22, 2026 | 1.1 s |
| Aug 29, 2026 | 1.1 s |
| Sep 5, 2026 | 1.2 s |
| Sep 12, 2026 | 1.2 s |
| Sep 19, 2026 | 1.1 s |
| Sep 26, 2026 | 1.1 s |
| Oct 3, 2026 | 1.1 s |
| Oct 10, 2026 | 1.0 s |
| Oct 17, 2026 | 1.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 110 ms |
| May 9, 2026 | 106 ms |
| May 16, 2026 | 105 ms |
| May 23, 2026 | 103 ms |
| May 30, 2026 | 103 ms |
| Jun 6, 2026 | 102 ms |
| Jun 13, 2026 | 103 ms |
| Jun 20, 2026 | 105 ms |
| Jun 27, 2026 | 108 ms |
| Jul 4, 2026 | 107 ms |
| Jul 11, 2026 | 110 ms |
| Jul 18, 2026 | 111 ms |
| Jul 25, 2026 | 105 ms |
| Aug 1, 2026 | 106 ms |
| Aug 8, 2026 | 110 ms |
| Aug 15, 2026 | 113 ms |
| Aug 22, 2026 | 117 ms |
| Aug 29, 2026 | 118 ms |
| Sep 5, 2026 | 121 ms |
| Sep 12, 2026 | 125 ms |
| Sep 19, 2026 | 140 ms |
| Sep 26, 2026 | 138 ms |
| Oct 3, 2026 | 139 ms |
| Oct 10, 2026 | 140 ms |
| Oct 17, 2026 | 136 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
Speed
Use efficient cache lifetimes
3.7 s · 2.3 MB31 files are served with short cache lifetimes, so returning visitors download them again (2.3 MB).
Improve image delivery
3.0 s · 2.4 MB9 images could be 2.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.0 s faster on a phone.
Render-blocking requests
1.0 s13 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.0 s.
Mobile performance score: 71
71/100Your mobile performance score is 71 (desktop: 92). Pages that score under 90 lose visitors before the first paint.
3 third-party services on the page
3 third-party services load with your homepage (Clarity, cdn-cookieyes.com and Google Fonts), adding 90 KiB and 85 ms of main-thread time.
1 long task on the main thread
1 long task block the main thread while loading, the longest for 58 ms. During a long task the page ignores taps.
Reduce unused CSS
21 KiBAbout 21 KiB of CSS is downloaded but never applied on this page.
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: 0.5 s
A phone's processor spends 0.5 s on main-thread work while loading, 224 ms of it running JavaScript. That is comfortably low.
Server response: 146 ms
146 msYour server sent the HTML in 146 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: 9.4 s
9.4 sYour largest element takes 9.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Transporto inovacijų forumas 2026”.
Time to Interactive: 9.6 s
9.6 sThe page becomes fully interactive after 9.6 s. Good is under 3.8 s.
Real-user CLS: 0.12
0.12For real visitors the layout shifts by 0.12 (75th percentile). Good is under 0.1.
Tap response (INP) got 28% slower for real visitors
+28%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 110 ms to 136 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 21% slower for real visitors
+21%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 0.9 s to 1.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 2.3 s
2.3 sThe first text or image appears after 2.3 s on a phone. Good is under 1.8 s.
Speed Index: 4.0 s
4.0 sVisually, the page fills in at 4.0 s (Speed Index). Good is under 3.4 s.
6 checks passed
Real-user LCP: 1.3 s
1.3 sReal visitors wait 1.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 120 ms
120 msReal visitors wait 120 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: 313 ms
313 msReal visitors wait 313 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.039
0.039The layout barely moves while loading (CLS 0.039, good is under 0.1).
Total Blocking Time: 8 ms
8 msScripts block the page for only 8 ms while loading. Good is under 200 ms.
Images and page weight
2 images over 500 KB
2 images weigh 1.5 MB together. On a phone connection a single image that size takes seconds.
10 images in older formats
10 images (2.9 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.
Page weight: 3.1 MB in 52 requests
3.1 MBYour homepage downloads 3.1 MB in 52 requests on a phone: images 2.9 MB (17), fonts 80 KiB (5) and scripts 52 KiB (7). Under 2 MB keeps phones on slow connections fast.
8 images below the first screen load straight away
8 images further down the page (2.7 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 0.9 g of CO₂ per visit
0.89 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.89 g of CO₂e: 106.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Scrollable region must have keyboard access (1 element)
Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.
Positive tabindex
1 element has a tabindex above 0, which scrambles the keyboard order.
All page content should be contained by landmarks (3 elements)
All page content should be contained by landmarks: 3 elements on the page fail this check, rated moderate by axe-core.
4 links without text
4 visible links have no text or label, so screen readers cannot say where they go.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 29 images in the HTML carry an alt attribute.
49 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 4 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Meta description is long (162 characters)
Your meta description is 162 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.
86 internal links, 20 external
The homepage links to 86 pages on litexpo.lt and 20 external pages.
6 checks passed
One H1 headline
Your main headline reads: “Lietuvos parodų ir kongresų centras LITEXPO”.
Title: 43 characters
Your title is a healthy 43 characters: “Lietuvos parodų ir kongresų centras LITEXPO”.
Canonical URL set
The canonical URL is https://www.litexpo.lt/.
Structured data in place
Structured data found: BreadcrumbList, WebPage and WebSite.
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.litexpo.lt/sitemap_index.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.litexpo.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 (625 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages without a meta description
https://www.litexpo.lt/maitinimas and https://www.litexpo.lt/lengvai-suprantama-kalba have no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://www.litexpo.lt/en has 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 49 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.
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
24 small tap targets
24 of 31 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
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.
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 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 343 words of copy
The homepage carries about 343 words of visible text.
3 checks passed
6 short forms
6 short forms (6 fields at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics, Microsoft Clarity and LinkedIn Insight.
Direct contact links
Visitors can reach you directly: 2 phone links and 2 email links.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads Microsoft Clarity (measured from a US location before any click). A consent tool (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.
4 cookies set on arrival
4Opening the homepage sets 4 cookies (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: CookieYes
A consent management tool (CookieYes) 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 litexpo.lt, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- WordPress
- Framework
- jQuery
- Analytics
- Google Analytics | Google Tag Manager | Microsoft Clarity
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 30 issues on litexpo.lt, including 12 speed issues, 2 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.