Tools & Wizards About Us
eriko.am screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

eriko.am

www.eriko.am

Page Load Speed

13.9 sec in total

First Response

3.2 sec

Resources Loaded

10.1 sec

Page Rendered

615 ms

eriko.am screenshot

About Website

Welcome to eriko.am homepage info - get ready to check Eriko best content for Armenia right away, or after learning these important things about eriko.am

description

Visit eriko.am

Key Findings

We analyzed Eriko.am page load time and found that the first response time was 3.2 sec and then it took 10.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster. This domain responded with an error, which can significantly jeopardize Eriko.am rating and web reputation

Performance Metrics

eriko.am performance score

0

Network Requests Diagram

eriko.am

3188 ms

www.eriko.am

459 ms

style.css

52 ms

slippry.css

56 ms

jquery.kwicks.css

63 ms

Our browser made a total of 99 requests to load all elements on the main page. We found that 44% of them (44 requests) were addressed to the original Eriko.am, 17% (17 requests) were made to Maps.google.com and 10% (10 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (6.2 sec) belongs to the original domain Eriko.am.

Page Optimization Overview & Recommendations

Page size can be reduced by 660.2 kB (17%)

Content Size

3.9 MB

After Optimization

3.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Eriko.am main page is 3.9 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. Images take 3.1 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 13.8 kB

  • Original 17.7 kB
  • After minification 17.3 kB
  • After compression 3.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 13.8 kB or 78% of the original size.

Image Optimization

-7%

Potential reduce by 207.5 kB

  • Original 3.1 MB
  • After minification 2.9 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. Eriko images are well optimized though.

JavaScript Optimization

-59%

Potential reduce by 415.1 kB

  • Original 704.7 kB
  • After minification 700.6 kB
  • After compression 289.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 415.1 kB or 59% of the original size.

CSS Optimization

-84%

Potential reduce by 23.8 kB

  • Original 28.4 kB
  • After minification 23.0 kB
  • After compression 4.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. Eriko.am needs all CSS files to be minified and compressed as it can save up to 23.8 kB or 84% of the original size.

Requests Breakdown

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

Requests Now

91

After Optimization

46

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 91 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Eriko. 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 6 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

eriko.am

eriko.am

3188 ms

www.eriko.am

www.eriko.am

459 ms

style.css

style.css

52 ms

slippry.css

slippry.css

56 ms

jquery.kwicks.css

jquery.kwicks.css

63 ms

jquery.fancybox-1.3.4.css

jquery.fancybox-1.3.4.css

55 ms

jquery.min.js

jquery.min.js

130 ms

jquery.fancybox-1.3.4.pack.js

jquery.fancybox-1.3.4.pack.js

82 ms

jquery.kwicks.min.js

jquery.kwicks.min.js

79 ms

slippry.min.js

slippry.min.js

81 ms

jquery.hoverIntent.js

jquery.hoverIntent.js

80 ms

ssubnav.min.js

ssubnav.min.js

87 ms

parallax.min.js

parallax.min.js

106 ms

functions.js

functions.js

106 ms

Christmas-Night-l.jpg

Christmas-Night-l.jpg

69 ms

gmap.html

gmap.html

62 ms

am.gif

am.gif

28 ms

ru.gif

ru.gif

28 ms

en.gif

en.gif

30 ms

bizol2.jpg

bizol2.jpg

3733 ms

hengst2.jpg

hengst2.jpg

110 ms

nordix4.jpg

nordix4.jpg

189 ms

valeo2.jpg

valeo2.jpg

157 ms

bizol-b.jpg

bizol-b.jpg

109 ms

valeo-b.jpg

valeo-b.jpg

110 ms

hengst-k.jpg

hengst-k.jpg

277 ms

Nordixlogo.png

Nordixlogo.png

140 ms

shadow.png

shadow.png

137 ms

DSC_0105.jpg

DSC_0105.jpg

6189 ms

10.jpg

10.jpg

168 ms

1.jpg

1.jpg

191 ms

%C3%8D%C3%A0%C3%B7%C3%A0%C3%AB%C3%AE%20%C3%AF%C3%B0%C3%A5%C3%A7%C3%A5%C3%AD%C3%B2%C3%A0%C3%B6%C3%A8%C3%A8.gif

%C3%8D%C3%A0%C3%B7%C3%A0%C3%AB%C3%AE%20%C3%AF%C3%B0%C3%A5%C3%A7%C3%A5%C3%AD%C3%B2%C3%A0%C3%B6%C3%A8%C3%A8.gif

199 ms

n1.jpg

n1.jpg

1323 ms

news2.jpg

news2.jpg

219 ms

1.jpg

1.jpg

281 ms

transp.png

transp.png

246 ms

divide-sm.png

divide-sm.png

276 ms

search-input-bg.png

search-input-bg.png

302 ms

search-btn.png

search-btn.png

303 ms

1.jpg

1.jpg

335 ms

sy-loader.gif

sy-loader.gif

328 ms

Christmas-Night-l.jpg

Christmas-Night-l.jpg

354 ms

js

js

44 ms

jquery-1.6.1.min.js

jquery-1.6.1.min.js

14 ms

jquery.gmap.js

jquery.gmap.js

353 ms

loader.gif

loader.gif

379 ms

likebox.php

likebox.php

231 ms

ebiMDO3r-8l.css

ebiMDO3r-8l.css

221 ms

jGc-59L_9lo.css

jGc-59L_9lo.css

223 ms

1kPfZUdGrka.js

1kPfZUdGrka.js

291 ms

Yuj_Y8xNH2C.js

Yuj_Y8xNH2C.js

381 ms

Mpe38fuBVZ2.js

Mpe38fuBVZ2.js

307 ms

n8qIhCw3vMx.js

n8qIhCw3vMx.js

288 ms

common.js

common.js

15 ms

map.js

map.js

14 ms

util.js

util.js

13 ms

geocoder.js

geocoder.js

12 ms

marker.js

marker.js

12 ms

onion.js

onion.js

31 ms

openhand_8_8.cur

openhand_8_8.cur

25 ms

AuthenticationService.Authenticate

AuthenticationService.Authenticate

66 ms

GeocodeService.Search

GeocodeService.Search

138 ms

marker.png

marker.png

6 ms

infowindow.js

infowindow.js

3 ms

controls.js

controls.js

29 ms

12002158_1617528225178660_2131773878272915377_n.png

12002158_1617528225178660_2131773878272915377_n.png

256 ms

1383196_1496417387289745_5731593699837701759_n.png

1383196_1496417387289745_5731593699837701759_n.png

297 ms

12241254_1014539455274883_1309349027958072130_n.jpg

12241254_1014539455274883_1309349027958072130_n.jpg

402 ms

12049494_199652660395781_976263455611622119_n.jpg

12049494_199652660395781_976263455611622119_n.jpg

373 ms

12801360_10153969511743007_4916688071288254198_n.jpg

12801360_10153969511743007_4916688071288254198_n.jpg

374 ms

12802957_101030503627305_3706733740528652376_n.jpg

12802957_101030503627305_3706733740528652376_n.jpg

376 ms

1930631_25833988885_2015_n.jpg

1930631_25833988885_2015_n.jpg

533 ms

wL6VQj7Ab77.png

wL6VQj7Ab77.png

83 ms

s7jcwEQH7Sx.png

s7jcwEQH7Sx.png

81 ms

StaticMapService.GetMapImage

StaticMapService.GetMapImage

137 ms

transparent.png

transparent.png

59 ms

css

css

54 ms

ViewportInfoService.GetViewportInfo

ViewportInfoService.GetViewportInfo

50 ms

stats.js

stats.js

31 ms

google4.png

google4.png

19 ms

mapcnt6.png

mapcnt6.png

32 ms

tmapctrl.png

tmapctrl.png

20 ms

cb_scout5.png

cb_scout5.png

36 ms

tmapctrl4.png

tmapctrl4.png

21 ms

imgs8.png

imgs8.png

36 ms

zN7GBFwfMP4uA6AR0HCoLQ.ttf

zN7GBFwfMP4uA6AR0HCoLQ.ttf

12 ms

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

12 ms

Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf

Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf

17 ms

d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf

d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf

16 ms

vt

vt

87 ms

vt

vt

81 ms

vt

vt

73 ms

vt

vt

8 ms

vt

vt

8 ms

vt

vt

75 ms

vt

vt

63 ms

VXcANLwwL5J.js

VXcANLwwL5J.js

41 ms

AmlxWlqMvlv.js

AmlxWlqMvlv.js

45 ms

QuotaService.RecordEvent

QuotaService.RecordEvent

25 ms

SEO Factors

eriko.am SEO score

0

Language and Encoding

  • Language Detected

    HY

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Eriko.am can be misinterpreted by Google and other search engines. Our service has detected that Armenian 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 Eriko.am 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

eriko.am

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