Tools & Wizards About Us
upese.lt screenshot

Report Summary

  • 13

    Performance

    Renders faster than
    25% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

upese.lt

Lietuvos upės - vandens kelionių Lietuvos upėmis vadovas

Page Load Speed

10.6 sec in total

First Response

4 sec

Resources Loaded

6.4 sec

Page Rendered

145 ms

upese.lt screenshot

About Website

Welcome to upese.lt homepage info - get ready to check Upese best content for Lithuania right away, or after learning these important things about upese.lt

Lietuvos upės, upeliai, ežerai. Aprašymai, vandens turizmo maršrutai, informacija, atstumai, sudėtingumas, nuotraukos, žemėlapiai. Plaukimas baidarėmis

Visit upese.lt

Key Findings

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

Performance Metrics

upese.lt performance score

13

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

22/100

10%

LCP (Largest Contentful Paint)

Value6.7 s

7/100

25%

SI (Speed Index)

Value19.1 s

0/100

10%

TBT (Total Blocking Time)

Value7,350 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.218

57/100

15%

TTI (Time to Interactive)

Value23.7 s

1/100

10%

Network Requests Diagram

upese.lt

4036 ms

css-098d3-55278.css

542 ms

css-396fd-03101.css

551 ms

js-00749-86122.js

713 ms

adsbygoogle.js

147 ms

Our browser made a total of 76 requests to load all elements on the main page. We found that 43% of them (33 requests) were addressed to the original Upese.lt, 12% (9 requests) were made to Googleads.g.doubleclick.net and 9% (7 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (4 sec) belongs to the original domain Upese.lt.

Page Optimization Overview & Recommendations

Page size can be reduced by 757.0 kB (49%)

Content Size

1.6 MB

After Optimization

800.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Upese.lt main page is 1.6 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. 70% of websites need less resources to load. Javascripts take 808.5 kB which makes up the majority of the site volume.

HTML Optimization

-91%

Potential reduce by 370.6 kB

  • Original 407.4 kB
  • After minification 403.4 kB
  • After compression 36.9 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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 370.6 kB or 91% of the original size.

Image Optimization

-10%

Potential reduce by 7.7 kB

  • Original 80.1 kB
  • After minification 72.4 kB

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. Upese images are well optimized though.

JavaScript Optimization

-20%

Potential reduce by 159.2 kB

  • Original 808.5 kB
  • After minification 808.2 kB
  • After compression 649.3 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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 159.2 kB or 20% of the original size.

CSS Optimization

-84%

Potential reduce by 219.5 kB

  • Original 261.7 kB
  • After minification 254.3 kB
  • After compression 42.2 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. Upese.lt needs all CSS files to be minified and compressed as it can save up to 219.5 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 48 (67%)

Requests Now

72

After Optimization

24

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

upese.lt

upese.lt

4036 ms

css-098d3-55278.css

css-098d3-55278.css

542 ms

css-396fd-03101.css

css-396fd-03101.css

551 ms

js-00749-86122.js

js-00749-86122.js

713 ms

adsbygoogle.js

adsbygoogle.js

147 ms

share42.js

share42.js

175 ms

system.css

system.css

122 ms

logo.png

logo.png

128 ms

baner_kr.png

baner_kr.png

129 ms

fv16x16.png

fv16x16.png

111 ms

fv2_16x16.png

fv2_16x16.png

112 ms

vandens_lygis.png

vandens_lygis.png

121 ms

istorija.png

istorija.png

437 ms

canoe.png

canoe.png

436 ms

links.png

links.png

437 ms

eu.png

eu.png

437 ms

grybai.png

grybai.png

437 ms

zuvys.png

zuvys.png

436 ms

lt.png

lt.png

641 ms

en.png

en.png

641 ms

ru.png

ru.png

641 ms

namas.png

namas.png

640 ms

explain.png

explain.png

641 ms

ULanim12.gif

ULanim12.gif

790 ms

gruzija.gif

gruzija.gif

1117 ms

Upi%C5%B3_baseinai.jpg

Upi%C5%B3_baseinai.jpg

788 ms

favicon12x12.png

favicon12x12.png

718 ms

phone.png

phone.png

720 ms

skype.png

skype.png

722 ms

messenger.png

messenger.png

828 ms

mailo.png

mailo.png

828 ms

show_ads_impl.js

show_ads_impl.js

407 ms

sdk.js

sdk.js

32 ms

hbg.jpg

hbg.jpg

755 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

757 ms

sdk.js

sdk.js

9 ms

292 ms

plusone.js

plusone.js

253 ms

analytics.js

analytics.js

264 ms

like.php

like.php

211 ms

like.php

like.php

215 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

55 ms

collect

collect

103 ms

zrt_lookup.html

zrt_lookup.html

162 ms

ads

ads

631 ms

js

js

123 ms

l0BHsWW2zGz.js

l0BHsWW2zGz.js

56 ms

FEppCFCt76d.png

FEppCFCt76d.png

53 ms

ads

ads

131 ms

ads

ads

376 ms

ads

ads

536 ms

ads

ads

378 ms

ads

ads

106 ms

7f032190f136c4d8e9a385e88120dc8d.js

7f032190f136c4d8e9a385e88120dc8d.js

31 ms

load_preloaded_resource.js

load_preloaded_resource.js

41 ms

dba2e8274bdef2cb1557de9a65e31c17.js

dba2e8274bdef2cb1557de9a65e31c17.js

42 ms

abg_lite.js

abg_lite.js

40 ms

window_focus.js

window_focus.js

60 ms

qs_click_protection.js

qs_click_protection.js

70 ms

ufs_web_display.js

ufs_web_display.js

21 ms

188a63c500db6a3aa7c42aa7d4186e28.js

188a63c500db6a3aa7c42aa7d4186e28.js

59 ms

icon.png

icon.png

31 ms

s

s

93 ms

css

css

71 ms

reactive_library.js

reactive_library.js

163 ms

ca-pub-6228753872125873

ca-pub-6228753872125873

92 ms

activeview

activeview

150 ms

6nBz8qVhgcmD6GxJa8R98i32RmIuiYHQQG15vc2mYdw.js

6nBz8qVhgcmD6GxJa8R98i32RmIuiYHQQG15vc2mYdw.js

62 ms

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrw2IJllpy8.woff

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrw2IJllpy8.woff

79 ms

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrwEIJllpy8.woff

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrwEIJllpy8.woff

80 ms

icons.png

icons.png

203 ms

sodar

sodar

190 ms

feedback_grey600_24dp.png

feedback_grey600_24dp.png

91 ms

fullscreen_api_adapter.js

fullscreen_api_adapter.js

89 ms

interstitial_ad_frame.js

interstitial_ad_frame.js

89 ms

settings_grey600_24dp.png

settings_grey600_24dp.png

111 ms

Accessibility Review

upese.lt accessibility score

75

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

Form elements do not have associated labels

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

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

upese.lt best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

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

Page has valid source maps

SEO Factors

upese.lt SEO score

100

Search Engine Optimization Advices

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

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

upese.lt

Open Graph description is not detected on the main page of Upese. 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: