Tools & Wizards About Us
dictionary.ge screenshot

Report Summary

  • 53

    Performance

    Renders faster than
    70% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

dictionary.ge

დიდი ინგლისურ-ქართული ონლაინ-ლექსიკონი | Dictionary.ge

Page Load Speed

4.8 sec in total

First Response

340 ms

Resources Loaded

4.4 sec

Page Rendered

77 ms

dictionary.ge screenshot

About Website

Welcome to dictionary.ge homepage info - get ready to check Dictionary best content for Georgia right away, or after learning these important things about dictionary.ge

დიდი ინგლისურ-ქართული ონლაინ-ლექსიკონი

Visit dictionary.ge

Key Findings

We analyzed Dictionary.ge page load time and found that the first response time was 340 ms and then it took 4.5 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

dictionary.ge performance score

53

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

45/100

10%

LCP (Largest Contentful Paint)

Value4.3 s

43/100

25%

SI (Speed Index)

Value6.1 s

44/100

10%

TBT (Total Blocking Time)

Value490 ms

59/100

30%

CLS (Cumulative Layout Shift)

Value0.038

100/100

15%

TTI (Time to Interactive)

Value18.4 s

3/100

10%

Network Requests Diagram

dictionary.ge

340 ms

dictionary.ge

878 ms

ka.css

327 ms

default.css

491 ms

div_based.css

491 ms

Our browser made a total of 73 requests to load all elements on the main page. We found that 59% of them (43 requests) were addressed to the original Dictionary.ge, 16% (12 requests) were made to Static.xx.fbcdn.net and 4% (3 requests) were made to T.dtscout.com. The less responsive or slowest element that took the longest time to load (1.5 sec) relates to the external source Counter.top.ge.

Page Optimization Overview & Recommendations

Page size can be reduced by 65.9 kB (32%)

Content Size

203.3 kB

After Optimization

137.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Dictionary.ge main page is 203.3 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 40% of websites need less resources to load. Images take 75.7 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 29.8 kB

  • Original 38.8 kB
  • After minification 36.6 kB
  • After compression 9.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 29.8 kB or 77% of the original size.

Image Optimization

-16%

Potential reduce by 12.4 kB

  • Original 75.7 kB
  • After minification 63.3 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. Obviously, Dictionary needs image optimization as it can save up to 12.4 kB or 16% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-17%

Potential reduce by 12.8 kB

  • Original 75.1 kB
  • After minification 71.1 kB
  • After compression 62.4 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 12.8 kB or 17% of the original size.

CSS Optimization

-80%

Potential reduce by 11.0 kB

  • Original 13.7 kB
  • After minification 11.0 kB
  • After compression 2.7 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. Dictionary.ge needs all CSS files to be minified and compressed as it can save up to 11.0 kB or 80% of the original size.

Requests Breakdown

Number of requests can be reduced by 49 (71%)

Requests Now

69

After Optimization

20

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

dictionary.ge

dictionary.ge

340 ms

dictionary.ge

dictionary.ge

878 ms

ka.css

ka.css

327 ms

default.css

default.css

491 ms

div_based.css

div_based.css

491 ms

scripts.js

scripts.js

497 ms

geokbd.js

geokbd.js

498 ms

cod

cod

1480 ms

s.js

s.js

30 ms

kbd_ka.gif

kbd_ka.gif

166 ms

header_l.gif

header_l.gif

224 ms

header_logo.gif

header_logo.gif

164 ms

header_title_ka.png

header_title_ka.png

164 ms

header_r.gif

header_r.gif

213 ms

menu_l.gif

menu_l.gif

169 ms

search_l.gif

search_l.gif

326 ms

kbd_en.gif

kbd_en.gif

327 ms

search_r.gif

search_r.gif

328 ms

lbt_l_c.gif

lbt_l_c.gif

333 ms

triangle_down_b.gif

triangle_down_b.gif

378 ms

lbt_r_c.gif

lbt_r_c.gif

392 ms

lbb_bl.gif

lbb_bl.gif

488 ms

lbb_br.gif

lbb_br.gif

488 ms

learners-250x47.png

learners-250x47.png

491 ms

google-play-129x38.png

google-play-129x38.png

497 ms

app-store-114x38.png

app-store-114x38.png

543 ms

barbarisms_v2_250x50.png

barbarisms_v2_250x50.png

562 ms

techdict_v2_250x50.png

techdict_v2_250x50.png

650 ms

biodict_250x30.png

biodict_250x30.png

650 ms

mildict_250x30.png

mildict_250x30.png

655 ms

box1_title_l.gif

box1_title_l.gif

660 ms

blank.gif

blank.gif

708 ms

box1_title_r.gif

box1_title_r.gif

730 ms

print.gif

print.gif

812 ms

box1_body_tr.gif

box1_body_tr.gif

812 ms

box1_body_bl.gif

box1_body_bl.gif

818 ms

box1_body_br.gif

box1_body_br.gif

823 ms

footer_corner_tl.gif

footer_corner_tl.gif

873 ms

footer_corner_tr.gif

footer_corner_tr.gif

899 ms

footer_logo.gif

footer_logo.gif

974 ms

footer_tsu.gif

footer_tsu.gif

974 ms

footer-lexico.png

footer-lexico.png

981 ms

header_bg.gif

header_bg.gif

985 ms

search_button_bg.gif

search_button_bg.gif

1024 ms

sdk.js

sdk.js

25 ms

next_b.gif

next_b.gif

1034 ms

sdk.js

sdk.js

6 ms

count222

count222

193 ms

300 ms

ga.js

ga.js

29 ms

107 ms

page.php

page.php

181 ms

__utm.gif

__utm.gif

15 ms

collect

collect

42 ms

tc.js

tc.js

59 ms

wHv3n85j7BM.css

wHv3n85j7BM.css

18 ms

DaPJf3IFK7Z.js

DaPJf3IFK7Z.js

25 ms

o1ndYS2og_B.js

o1ndYS2og_B.js

22 ms

wxP3i94d1BQ.js

wxP3i94d1BQ.js

51 ms

s23ZuKml3wQ.js

s23ZuKml3wQ.js

22 ms

xnXjJZlUWr1.js

xnXjJZlUWr1.js

22 ms

TI6H6YJnuJW.js

TI6H6YJnuJW.js

20 ms

dHtBGdhg2uK.js

dHtBGdhg2uK.js

23 ms

p55HfXW__mM.js

p55HfXW__mM.js

49 ms

ALTQi95mOyD.js

ALTQi95mOyD.js

55 ms

240429222_309047501019666_6154925901279048318_n.jpg

240429222_309047501019666_6154925901279048318_n.jpg

25 ms

wuH-1da_5h_.js

wuH-1da_5h_.js

11 ms

240664852_309047494353000_4461880678672206359_n.jpg

240664852_309047494353000_4461880678672206359_n.jpg

11 ms

UXtr_j2Fwe-.png

UXtr_j2Fwe-.png

5 ms

192 ms

tag.min.js

tag.min.js

27 ms

213 ms

lt.min.js

lt.min.js

14 ms

Accessibility Review

dictionary.ge accessibility score

73

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.

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

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

dictionary.ge best practices score

67

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

High

Browser errors were logged to the console

SEO Factors

dictionary.ge SEO score

69

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

Language and Encoding

  • Language Detected

    KA

  • Language Claimed

    KA

  • Encoding

    UTF-8

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

dictionary.ge

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