Tools & Wizards About Us

Report Summary

  • 14

    Performance

    Renders faster than
    26% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

mobile.lt

Automobiliai iš Europos | Mobile.de | BRC Autocentras

Page Load Speed

5 sec in total

First Response

376 ms

Resources Loaded

4 sec

Page Rendered

620 ms

About Website

Click here to check amazing Mobile content for Lithuania. Otherwise, check out these important facts you probably never knew about mobile.lt

Patikimas naudotų automobilių pardavėjas Mobile.de. BRC autocentras - oficialus Mobile.de partneris jau 20 metų. Siūlomi tvarkingi visų markių naudoti automobiliai iš Europos.

Visit mobile.lt

Key Findings

We analyzed Mobile.lt page load time and found that the first response time was 376 ms and then it took 4.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

mobile.lt performance score

14

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

47/100

10%

LCP (Largest Contentful Paint)

Value14.4 s

0/100

25%

SI (Speed Index)

Value9.4 s

12/100

10%

TBT (Total Blocking Time)

Value2,710 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.262

47/100

15%

TTI (Time to Interactive)

Value16.1 s

6/100

10%

Network Requests Diagram

mobile.lt

376 ms

480 ms

mobile

242 ms

mobile

415 ms

js.cookie.js

15 ms

Our browser made a total of 45 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Mobile.lt, 76% (34 requests) were made to Lt.brcauto.eu and 7% (3 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.6 sec) relates to the external source Lt.brcauto.eu.

Page Optimization Overview & Recommendations

Page size can be reduced by 322.1 kB (7%)

Content Size

4.9 MB

After Optimization

4.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Mobile.lt main page is 4.9 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 45% of websites need less resources to load. Images take 4.6 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 67.5 kB

  • Original 88.0 kB
  • After minification 69.3 kB
  • After compression 20.4 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. This page needs HTML code to be minified as it can gain 18.7 kB, which is 21% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 67.5 kB or 77% of the original size.

Image Optimization

-5%

Potential reduce by 247.6 kB

  • Original 4.6 MB
  • After minification 4.3 MB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Mobile images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 420 B

  • Original 195.0 kB
  • After minification 195.0 kB
  • After compression 194.6 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. This website has mostly compressed JavaScripts.

CSS Optimization

-9%

Potential reduce by 6.5 kB

  • Original 72.0 kB
  • After minification 72.0 kB
  • After compression 65.5 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Mobile.lt has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 15 (45%)

Requests Now

33

After Optimization

18

  • Images
  • JavaScript
  • CSS

The browser has sent 33 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Mobile. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

Accessibility Review

mobile.lt accessibility score

84

Accessibility Issues

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Buttons do not have an accessible name

High

Links do not have a discernible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

mobile.lt best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

mobile.lt SEO score

91

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    LT

  • Language Claimed

    LT

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mobile.lt can be misinterpreted by Google and other search engines. Our service has detected that Lithuanian is used on the page, and it matches the claimed language. Our system also found out that Mobile.lt main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

Open Graph description is not detected on the main page of Mobile. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: