Report Summary

  • 100

    Performance

    Renders faster than
    97% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 87% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

nafig.eu

nafig.eu - Užregistruotas domenas - Interneto vizija

Page Load Speed

4.9 sec in total

First Response

866 ms

Resources Loaded

3.3 sec

Page Rendered

760 ms

nafig.eu screenshot

About Website

Click here to check amazing Nafig content for Lithuania. Otherwise, check out these important facts you probably never knew about nafig.eu

Tiktai seni geri laiko patikrinti filmai

Visit nafig.eu

Key Findings

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

Performance Metrics

nafig.eu performance score

100

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.4 s

98/100

10%

LCP (Largest Contentful Paint)

Value1.4 s

100/100

25%

SI (Speed Index)

Value2.1 s

99/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value1.4 s

100/100

10%

Network Requests Diagram

www.nafig.eu

866 ms

style.css

234 ms

widget.css

232 ms

RBL_UI.css

234 ms

postratings-css.css

234 ms

Our browser made a total of 73 requests to load all elements on the main page. We found that 96% of them (70 requests) were addressed to the original Nafig.eu, 3% (2 requests) were made to Google-analytics.com and 1% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Nafig.eu.

Page Optimization Overview & Recommendations

Page size can be reduced by 318.5 kB (18%)

Content Size

1.8 MB

After Optimization

1.5 MB

In fact, the total size of Nafig.eu main page is 1.8 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. 60% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 97.3 kB

  • Original 113.8 kB
  • After minification 106.2 kB
  • After compression 16.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. 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 97.3 kB or 86% of the original size.

Image Optimization

-4%

Potential reduce by 52.8 kB

  • Original 1.4 MB
  • After minification 1.4 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. Nafig images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 140.6 kB

  • Original 221.3 kB
  • After minification 207.6 kB
  • After compression 80.7 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 140.6 kB or 64% of the original size.

CSS Optimization

-80%

Potential reduce by 27.8 kB

  • Original 34.9 kB
  • After minification 30.0 kB
  • After compression 7.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. Nafig.eu needs all CSS files to be minified and compressed as it can save up to 27.8 kB or 80% of the original size.

Requests Breakdown

Number of requests can be reduced by 21 (29%)

Requests Now

72

After Optimization

51

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

Accessibility Review

nafig.eu accessibility score

95

Accessibility Issues

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

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

SEO Factors

nafig.eu SEO score

77

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Page is blocked from indexing

High

robots.txt is not valid

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Nafig.eu can be misinterpreted by Google and other search engines. Our service has detected that Lithuanian is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Nafig.eu 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 Nafig. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: