10.8 sec in total
481 ms
10.2 sec
192 ms
Click here to check amazing Eqe content for Georgia. Otherwise, check out these important facts you probably never knew about eqe.ge
Visit eqe.geWe analyzed Eqe.ge page load time and found that the first response time was 481 ms and then it took 10.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.
eqe.ge performance score
name
value
score
weighting
Value2.7 s
59/100
10%
Value12.9 s
0/100
25%
Value8.6 s
17/100
10%
Value290 ms
79/100
30%
Value0.153
75/100
15%
Value15.3 s
7/100
10%
481 ms
1199 ms
1353 ms
902 ms
456 ms
Our browser made a total of 98 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Eqe.ge, 60% (59 requests) were made to Eqe.gov.ge and 14% (14 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (5.8 sec) relates to the external source Eqe.gov.ge.
Page size can be reduced by 1.7 MB (53%)
3.1 MB
1.5 MB
In fact, the total size of Eqe.ge main page is 3.1 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. 50% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 58.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 58.9 kB or 83% of the original size.
Potential reduce by 139.1 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, Eqe needs image optimization as it can save up to 139.1 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 811.8 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 811.8 kB or 72% of the original size.
Potential reduce by 653.4 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. Eqe.ge needs all CSS files to be minified and compressed as it can save up to 653.4 kB or 94% of the original size.
Number of requests can be reduced by 46 (52%)
89
43
The browser has sent 89 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Eqe. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
eqe.ge
481 ms
eqe.gov.ge
1199 ms
bootstrap.css.map
1353 ms
bootstrap.css
902 ms
awesome.css
456 ms
reset.css
310 ms
default.css
460 ms
default-responsive.css
459 ms
owl.carousel.css
462 ms
grey.css
609 ms
colorbox.css
610 ms
select2.css
764 ms
animate.css
1066 ms
select2-bootstrap.css
761 ms
style.css
767 ms
jquery.js
1373 ms
easing.js
919 ms
bootstrap.js
924 ms
colorbox.js
1050 ms
bootstrap.min.js
1222 ms
owl.carousel.js
1232 ms
icheck.min.js
1201 ms
print.js
1216 ms
select2.js
1655 ms
cookie.js
1368 ms
scripts.js
1395 ms
poll.js
1105 ms
analytics.js
23 ms
logo.png
166 ms
2014110321043387130.png
323 ms
2014110321023431811.png
315 ms
2014110321034617382.png
319 ms
2014110321093759542.png
491 ms
2015012220150519035.jpg
1235 ms
2015012218045323765.png
772 ms
2015082417152469376.jpg
493 ms
2015012218062250248.png
493 ms
calendar_left.png
490 ms
calendar_right.png
652 ms
crop.img
1024 ms
crop.img
726 ms
crop.img
918 ms
crop.img
892 ms
home.png
877 ms
phone.png
925 ms
envelope.png
1028 ms
2014110421304869549.png
1044 ms
2014111917010791238.png
1067 ms
2014111916595243768.png
1078 ms
2014111916570598068.png
1178 ms
2014111917044971749.png
1178 ms
2014111917022238708.png
1197 ms
2014111917053379598.png
1219 ms
2014111916555171231.png
1250 ms
artmedia.png
1330 ms
sdk.js
15 ms
close.png
1315 ms
loader.GIF
1334 ms
embed
146 ms
collect
67 ms
grey.png
1290 ms
92 ms
xd_arbiter.php
31 ms
xd_arbiter.php
39 ms
js
79 ms
init_embed.js
33 ms
common.js
37 ms
map.js
47 ms
google4.png
56 ms
overlay.js
55 ms
util.js
74 ms
onion.js
70 ms
search_impl.js
72 ms
StaticMapService.GetMapImage
179 ms
stats.js
88 ms
openhand_8_8.cur
63 ms
ViewportInfoService.GetViewportInfo
67 ms
ViewportInfoService.GetViewportInfo
123 ms
kh
134 ms
transparent.png
59 ms
controls.js
34 ms
css
80 ms
entity11.png
39 ms
vt
81 ms
vt
78 ms
vt
73 ms
vt
83 ms
mapcnt6.png
29 ms
tmapctrl.png
34 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
40 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
43 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
50 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
51 ms
AuthenticationService.Authenticate
22 ms
font.ttf
5817 ms
fontawesome.ttf
374 ms
font.ttf
227 ms
QuotaService.RecordEvent
15 ms
eqe.ge accessibility score
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
Buttons do not have an accessible name
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
eqe.ge best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
eqe.ge SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
KA
GE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Eqe.ge can be misinterpreted by Google and other search engines. Our service has detected that Georgian is used on the page, and it does not match the claimed language. Our system also found out that Eqe.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.
eqe.ge
Open Graph description is not detected on the main page of Eqe. 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: