Tools & Wizards About Us
explainers.lt screenshot

Report Summary

  • 33

    Performance

    Renders faster than
    53% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

explainers.lt

Awesome and professional Explainer videos for Your Business

Page Load Speed

6.6 sec in total

First Response

1.5 sec

Resources Loaded

4.6 sec

Page Rendered

567 ms

explainers.lt screenshot

About Website

Visit explainers.lt now to see the best up-to-date Explainer S content and also check out these interesting facts you probably never knew about explainers.lt

No two businesses are the same, so all explainer videos deserve to be unique as well. You can rest assured knowing that your video will be tailored to fit the special demands of Your business. We work...

Visit explainers.lt

Key Findings

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

Performance Metrics

explainers.lt performance score

33

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

51/100

10%

LCP (Largest Contentful Paint)

Value5.7 s

16/100

25%

SI (Speed Index)

Value8.0 s

22/100

10%

TBT (Total Blocking Time)

Value1,290 ms

18/100

30%

CLS (Cumulative Layout Shift)

Value0.058

98/100

15%

TTI (Time to Interactive)

Value11.6 s

18/100

10%

Network Requests Diagram

explainers.lt

1512 ms

style.min.css

37 ms

styles.css

48 ms

portfolio.css

48 ms

style.css

79 ms

Our browser made a total of 76 requests to load all elements on the main page. We found that 76% of them (58 requests) were addressed to the original Explainers.lt, 13% (10 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Explainers.lt.

Page Optimization Overview & Recommendations

Page size can be reduced by 112.1 kB (11%)

Content Size

1.0 MB

After Optimization

910.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-79%

Potential reduce by 100.8 kB

  • Original 127.8 kB
  • After minification 125.0 kB
  • After compression 27.0 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 100.8 kB or 79% of the original size.

Image Optimization

-1%

Potential reduce by 2.1 kB

  • Original 303.8 kB
  • After minification 301.7 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. Explainer S images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 5.3 kB

  • Original 460.6 kB
  • After minification 460.6 kB
  • After compression 455.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. This website has mostly compressed JavaScripts.

CSS Optimization

-3%

Potential reduce by 3.9 kB

  • Original 130.7 kB
  • After minification 130.7 kB
  • After compression 126.8 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. Explainers.lt has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 51 (80%)

Requests Now

64

After Optimization

13

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

explainers.lt

explainers.lt

1512 ms

style.min.css

style.min.css

37 ms

styles.css

styles.css

48 ms

portfolio.css

portfolio.css

48 ms

style.css

style.css

79 ms

font-awesome-legacy.min.css

font-awesome-legacy.min.css

29 ms

grid-system.css

grid-system.css

45 ms

style.css

style.css

54 ms

element-toggles.css

element-toggles.css

70 ms

element-video-lightbox.css

element-video-lightbox.css

414 ms

caroufredsel.css

caroufredsel.css

67 ms

cf7.css

cf7.css

66 ms

css

css

44 ms

responsive.css

responsive.css

68 ms

ascend.css

ascend.css

71 ms

menu-dynamic.css

menu-dynamic.css

77 ms

js_composer.min.css

js_composer.min.css

78 ms

salient-dynamic-styles.css

salient-dynamic-styles.css

80 ms

css

css

63 ms

jquery.min.js

jquery.min.js

567 ms

jquery-migrate.min.js

jquery-migrate.min.js

432 ms

js

js

138 ms

email-decode.min.js

email-decode.min.js

9 ms

animate.min.css

animate.min.css

25 ms

style-non-critical.css

style-non-critical.css

18 ms

jquery.fancybox.css

jquery.fancybox.css

369 ms

core.css

core.css

38 ms

index.js

index.js

392 ms

index.js

index.js

408 ms

imagesLoaded.min.js

imagesLoaded.min.js

830 ms

isotope.min.js

isotope.min.js

846 ms

salient-portfolio.js

salient-portfolio.js

378 ms

touchswipe.min.js

touchswipe.min.js

388 ms

caroufredsel.min.js

caroufredsel.min.js

2093 ms

salient-social.js

salient-social.js

851 ms

jquery.easing.min.js

jquery.easing.min.js

850 ms

jquery.mousewheel.min.js

jquery.mousewheel.min.js

852 ms

priority.js

priority.js

1124 ms

transit.min.js

transit.min.js

1204 ms

waypoints.js

waypoints.js

1205 ms

hoverintent.min.js

hoverintent.min.js

1204 ms

jquery.fancybox.js

jquery.fancybox.js

1344 ms

anime.min.js

anime.min.js

1490 ms

superfish.js

superfish.js

1563 ms

init.js

init.js

1219 ms

api.js

api.js

46 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

1568 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

1590 ms

wp-polyfill.min.js

wp-polyfill.min.js

1815 ms

index.js

index.js

1856 ms

js_composer_front.min.js

js_composer_front.min.js

1922 ms

v84a3a4012de94ce1a686ba8c167c359c1696973893317

v84a3a4012de94ce1a686ba8c167c359c1696973893317

70 ms

Explainers.lt_logo.png

Explainers.lt_logo.png

1541 ms

video-1st-frame-min-1.png

video-1st-frame-min-1.png

1741 ms

Apie-Sriuba-still-600x403.jpg

Apie-Sriuba-still-600x403.jpg

1793 ms

Apie-Uteles-still-600x403.jpg

Apie-Uteles-still-600x403.jpg

1847 ms

Svajok-LT-600x403.jpg

Svajok-LT-600x403.jpg

1912 ms

237 ms

explainer-video-homepage-background.png

explainer-video-homepage-background.png

1832 ms

explainer-video-production-steps.png

explainer-video-production-steps.png

1872 ms

explainer-video-timing.png

explainer-video-timing.png

2034 ms

explainer-video-pricing.png

explainer-video-pricing.png

2070 ms

explainer-videos-FAQ.png

explainer-videos-FAQ.png

2128 ms

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

107 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

138 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

160 ms

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

161 ms

XRXI3I6Li01BKofiOc5wtlZ2di8HDOUhdTQ3ig.ttf

XRXI3I6Li01BKofiOc5wtlZ2di8HDOUhdTQ3ig.ttf

161 ms

XRXI3I6Li01BKofiOc5wtlZ2di8HDFwmdTQ3ig.ttf

XRXI3I6Li01BKofiOc5wtlZ2di8HDFwmdTQ3ig.ttf

161 ms

icomoon.woff

icomoon.woff

2131 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf

66 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf

63 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf

65 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf

66 ms

18 ms

recaptcha__en.js

recaptcha__en.js

38 ms

Accessibility Review

explainers.lt accessibility score

85

Accessibility Issues

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

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

Links do not have a discernible name

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

explainers.lt best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

explainers.lt SEO score

92

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Explainers.lt can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Explainers.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

explainers.lt

Open Graph data is detected on the main page of Explainer S. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: