Report Summary

  • 32

    Performance

    Renders faster than
    52% of other websites

  • 65

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 89

    SEO

    Google-friendlier than
    67% of websites

gf.lt

Vartojimo paskolos internetu | GENERAL FINANCING BANKAS

Page Load Speed

12.7 sec in total

First Response

413 ms

Resources Loaded

11.9 sec

Page Rendered

420 ms

gf.lt screenshot

About Website

Visit gf.lt now to see the best up-to-date Gf content for Lithuania and also check out these interesting facts you probably never knew about gf.lt

Planuojate naujų pirkinių įsigijimą ar būsto remontą? Sužinokite palankias General Financing sąlygas ir svajones įgyvendinkite lengvai!

Visit gf.lt

Key Findings

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

Performance Metrics

gf.lt performance score

32

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

45/100

10%

LCP (Largest Contentful Paint)

Value7.5 s

4/100

25%

SI (Speed Index)

Value11.2 s

5/100

10%

TBT (Total Blocking Time)

Value800 ms

37/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value19.7 s

2/100

10%

Network Requests Diagram

gf.lt

413 ms

www.gf.lt

1402 ms

cms2.css

355 ms

jquery.lightbox.css

353 ms

module.css

354 ms

Our browser made a total of 102 requests to load all elements on the main page. We found that 82% of them (84 requests) were addressed to the original Gf.lt, 7% (7 requests) were made to Gf.livechat.lt and 3% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (5.5 sec) belongs to the original domain Gf.lt.

Page Optimization Overview & Recommendations

Page size can be reduced by 261.3 kB (5%)

Content Size

5.2 MB

After Optimization

4.9 MB

In fact, the total size of Gf.lt main page is 5.2 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.9 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 30.7 kB

  • Original 39.6 kB
  • After minification 34.2 kB
  • After compression 8.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. This page needs HTML code to be minified as it can gain 5.5 kB, which is 14% 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 30.7 kB or 78% of the original size.

Image Optimization

-3%

Potential reduce by 130.5 kB

  • Original 4.9 MB
  • After minification 4.8 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. Gf images are well optimized though.

JavaScript Optimization

-41%

Potential reduce by 95.1 kB

  • Original 230.2 kB
  • After minification 230.1 kB
  • After compression 135.1 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 95.1 kB or 41% of the original size.

CSS Optimization

-76%

Potential reduce by 5.0 kB

  • Original 6.5 kB
  • After minification 6.4 kB
  • After compression 1.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. Gf.lt needs all CSS files to be minified and compressed as it can save up to 5.0 kB or 76% of the original size.

Requests Breakdown

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

Requests Now

98

After Optimization

54

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

Accessibility Review

gf.lt accessibility score

65

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

[role]s are not contained by their required parent element

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

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

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

gf.lt best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

gf.lt SEO score

89

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

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Gf.lt can be misinterpreted by Google and other search engines. Our service has detected that Lithuanian is used on the page, and it does not match the claimed English language. Our system also found out that Gf.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 data is detected on the main page of Gf. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: