Website review, no card needed

lattelecom.lv logo

lattelecom.lv website review

Visit site (opens in a new tab)Reviewed 1 November 202637 issues · 84 checks

This review found 37 issues worth fixing on lattelecom.lv, 15 of them high impact, across 84 checks. The most urgent: use efficient cache lifetimes. 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
2.3 s1.8 sMay 9Oct 241.9 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.2 s
May 16, 20262.1 s
May 23, 20262.1 s
May 30, 20262.1 s
Jun 6, 20262.1 s
Jun 13, 20262.1 s
Jun 20, 20262.1 s
Jun 27, 20262.2 s
Jul 4, 20262.2 s
Jul 11, 20262.2 s
Jul 18, 20262.2 s
Jul 25, 20262.2 s
Aug 1, 20262.2 s
Aug 8, 20262.1 s
Aug 15, 20262.1 s
Aug 22, 20262.0 s
Aug 29, 20262.0 s
Sep 5, 20262.0 s
Sep 12, 20261.9 s
Sep 19, 20261.9 s
Sep 26, 20261.9 s
Oct 3, 20262.0 s
Oct 10, 20261.9 s
Oct 17, 20261.9 s
Oct 24, 20261.9 s
Real-visitor tap response (INP)75th percentile, phones
299 ms232 msMay 9Oct 24247 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026291 ms
May 16, 2026287 ms
May 23, 2026281 ms
May 30, 2026276 ms
Jun 6, 2026273 ms
Jun 13, 2026271 ms
Jun 20, 2026273 ms
Jun 27, 2026275 ms
Jul 4, 2026267 ms
Jul 11, 2026258 ms
Jul 18, 2026248 ms
Jul 25, 2026241 ms
Aug 1, 2026240 ms
Aug 8, 2026244 ms
Aug 15, 2026246 ms
Aug 22, 2026251 ms
Aug 29, 2026249 ms
Sep 5, 2026246 ms
Sep 12, 2026247 ms
Sep 19, 2026246 ms
Sep 26, 2026246 ms
Oct 3, 2026245 ms
Oct 10, 2026243 ms
Oct 17, 2026243 ms
Oct 24, 2026247 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 lattelecom.lv (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. lattelecom.lv at 1.6 s1.6 s
  2. lattelecom.lv at 3.1 s3.1 s
  3. lattelecom.lv at 4.7 s4.7 s
  4. lattelecom.lv at 6.3 s6.3 s
  5. lattelecom.lv at 7.9 s7.9 s
  6. lattelecom.lv at 9.4 s9.4 s
  7. lattelecom.lv at 11.0 s11.0 s
  8. lattelecom.lv at 12.6 s12.6 s

Speed

11 to fix45
  • Use efficient cache lifetimes

    2.1 s · 511 KiB

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

  • Render-blocking requests

    1.4 s

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

  • Mobile performance score: 45

    45/100

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

  • Main-thread work: 6.8 s

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

  • 3,048 HTML elements

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

  • Reduce unused JavaScript

    900 ms · 437 KiB

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

  • 5 third-party services on the page

    5 third-party services load with your homepage (Cookie-Script.com, Google Tag Manager and weglot.com and others), adding 770 KiB and 954 ms of main-thread time.

  • Improve image delivery

    700 ms · 94 KiB

    1 image could be 94 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 700 ms faster on a phone.

  • Cookie-Script.com adds 531 ms

    531 ms

    Cookie-Script.com costs a phone 531 ms of main-thread work and 49 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.

  • 15 long tasks on the main thread

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

  • LiveChat adds 35 ms

    35 ms

    LiveChat costs a phone 35 ms of main-thread work and 418 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.

  • Legacy JavaScript

    50 ms · 4 KiB

    Polyfills for old browsers add 4 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 50 ms faster on a phone.

  • Reduce unused CSS

    33 KiB

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

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

    282 ms

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

Core Web Vitals

7 to fix67
  • 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: 11.5 s

    11.5 s

    Your largest element takes 11.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Mūsu tīmekļa vietnē tiek izmantotas sīkdatnes, lai nodrošin…”. Most of its time is element render delay (5.3 s).

  • Speed Index: 11.9 s

    11.9 s

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

  • Time to Interactive: 14.9 s

    14.9 s

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

  • Total Blocking Time: 834 ms

    834 ms

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

  • Real-user INP: 246 ms

    246 ms

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

  • First Contentful Paint: 1.9 s

    1.9 s

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

7 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 CLS: 0.00

    0.00

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

  • Real-user FCP: 1.5 s

    1.5 s

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

  • Real-user TTFB: 659 ms

    659 ms

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

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

    -15%

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

  • Largest content (LCP) got 13% faster for real visitors

    -13%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.2 s to 1.9 s 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 fix85
  • Page weight: 2.3 MB in 158 requests

    2.3 MB

    Your homepage downloads 2.3 MB in 158 requests on a phone: scripts 1.5 MB (96), fonts 368 KiB (5) and images 209 KiB (8). Under 2 MB keeps phones on slow connections fast.

  • About 0.7 g of CO₂ per visit

    0.66 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.66 g of CO₂e: 78.7 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

8 to fixGoogle 9091
  • Invalid ARIA attributes

    1 element use ARIA attributes their role does not allow, which confuses screen readers.

  • ARIA commands must have an accessible name (3 elements)

    ARIA commands must have an accessible name: 3 elements on the page fail this check, rated serious by axe-core.

  • Interactive controls must not be nested (1 element)

    Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

  • Document should not have more than one contentinfo landmark (1 element)

    Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

  • 8 links without text

    8 visible links have no text or label, so screen readers cannot say where they go.

  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Headings should not be empty (1 element)

    Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

2 checks passed
  • Every image has alt text

    All 39 images in the HTML carry an alt attribute.

  • 55 automated accessibility rules passed

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

SEO

3 to fixGoogle 10087
  • No structured data

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

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • One H1 headline

    Your <h1> is empty.

  • 115 internal links, 8 external

    The homepage links to 115 pages on lattelecom.lv and 8 external pages.

5 checks passed
  • Meta description: 112 characters

    Your meta description is 112 characters: “Stabils optiskais internets un moderna televīzija ar aizraujošu TV saturu! Pārnākt pie Tet ir viegli! Ieskaties!”.

  • Title: 54 characters

    Your title is a healthy 54 characters: “Tet televīzija, internets un elektrība vieno! | Tet.lv”.

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

  • XML sitemap found

    Your XML sitemap is reachable at https://www.tet.lv/sitemap.xml.

AI search readiness

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

  • Some text only appears after JavaScript runs

    36%

    The HTML your server sends has 725 of the 1,999 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

  • No llms.txt

    There is no https://www.tet.lv/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.

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

Other pages

100
  • 6 pages slow to respond

    https://www.tet.lv/akcijas, https://www.tet.lv/veikals/televizori/tcl-55-uhd-qd-mini-led-google-tv-55q6c.html, https://www.tet.lv/veikals/viedtalruni/apple-iphone-18-pro-256gb-burgundy.html, https://www.tet.lv/veikals/gaisa-silditaji/mill-oil2000wifi3.html, https://www.tet.lv/veikals/gaisa-sausinataji/xiaomi-smart-dehumidifier-lite-bhr8374eu.html and https://www.tet.lv/veikals/matu-veidotaji/dyson-hs09-airwrap-co-anda2x-straight-wavy-ceramic-pink-rose-gold-598757-01.html took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 56 found) and read each the way a search engine does.

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

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • 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 15 pages that loaded have a <title>.

Best practices

1 to fixGoogle 7797
  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    80 of 99 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix58
  • 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 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 1,999 words of copy

    The homepage carries about 1,999 words of visible text.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

3 checks passed
  • 3 short forms

    3 short forms (0 fields at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 50 testimonial or review blocks and 2 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

1 to fix
  • 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). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

  • 14 cookies set on arrival

    14

    Opening the homepage sets 14 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.

  • 7 other companies contacted

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

Upkeep, stack and company

Stack

CMS
Joomla
Analytics
Google Tag Manager
Hosting
SIA Tet

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 37 issues on lattelecom.lv, including 18 speed issues, 3 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