Tools & Wizards About Us
steko.am screenshot

Report Summary

  • 25

    Performance

    Renders faster than
    44% of other websites

  • 51

    Accessibility

    Visual factors better than
    that of 21% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

steko.am

STEKO

Page Load Speed

2.4 sec in total

First Response

359 ms

Resources Loaded

1.7 sec

Page Rendered

358 ms

steko.am screenshot

About Website

Visit steko.am now to see the best up-to-date STEKO content for Armenia and also check out these interesting facts you probably never knew about steko.am

Visit steko.am

Key Findings

We analyzed Steko.am page load time and found that the first response time was 359 ms and then it took 2.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

steko.am performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.9 s

11/100

10%

LCP (Largest Contentful Paint)

Value14.6 s

0/100

25%

SI (Speed Index)

Value10.8 s

6/100

10%

TBT (Total Blocking Time)

Value1,520 ms

13/100

30%

CLS (Cumulative Layout Shift)

Value0.099

90/100

15%

TTI (Time to Interactive)

Value6.5 s

58/100

10%

Network Requests Diagram

steko.am

359 ms

jquery-2.1.3.js

296 ms

materialize.css

265 ms

materialize.js

351 ms

bootstrap.css

262 ms

Our browser made a total of 38 requests to load all elements on the main page. We found that 97% of them (37 requests) were addressed to the original Steko.am, 3% (1 request) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (847 ms) belongs to the original domain Steko.am.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.3 MB (20%)

Content Size

6.5 MB

After Optimization

5.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Steko.am main page is 6.5 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 5.4 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 18.8 kB

  • Original 22.6 kB
  • After minification 18.9 kB
  • After compression 3.7 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 3.6 kB, which is 16% 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 18.8 kB or 83% of the original size.

Image Optimization

-6%

Potential reduce by 337.8 kB

  • Original 5.4 MB
  • After minification 5.0 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. STEKO images are well optimized though.

JavaScript Optimization

-82%

Potential reduce by 555.8 kB

  • Original 675.6 kB
  • After minification 426.2 kB
  • After compression 119.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 555.8 kB or 82% of the original size.

CSS Optimization

-86%

Potential reduce by 385.4 kB

  • Original 448.5 kB
  • After minification 351.6 kB
  • After compression 63.1 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. Steko.am needs all CSS files to be minified and compressed as it can save up to 385.4 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 20 (56%)

Requests Now

36

After Optimization

16

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

steko.am

steko.am

359 ms

jquery-2.1.3.js

jquery-2.1.3.js

296 ms

materialize.css

materialize.css

265 ms

materialize.js

materialize.js

351 ms

bootstrap.css

bootstrap.css

262 ms

font-awesome.min.css

font-awesome.min.css

170 ms

bootstrap.min.js

bootstrap.min.js

172 ms

jquery.easing.min.js

jquery.easing.min.js

253 ms

sliiide.js

sliiide.js

256 ms

main.js

main.js

337 ms

reset.css

reset.css

341 ms

modernizr.js

modernizr.js

342 ms

jquery.mixitup.min.js

jquery.mixitup.min.js

342 ms

component.css

component.css

394 ms

style.css

style.css

419 ms

normalize.css

normalize.css

427 ms

stylesheet.css

stylesheet.css

422 ms

magnific-popup.css

magnific-popup.css

420 ms

jquery.magnific-popup.js

jquery.magnific-popup.js

430 ms

preloader.js

preloader.js

452 ms

js

js

33 ms

RichMarker.js

RichMarker.js

517 ms

nav-icon.css

nav-icon.css

82 ms

steko_logo_w.png

steko_logo_w.png

241 ms

steko_logo.png

steko_logo.png

242 ms

timthumb.php

timthumb.php

847 ms

timthumb.php

timthumb.php

660 ms

timthumb.php

timthumb.php

739 ms

timthumb.php

timthumb.php

565 ms

timthumb.php

timthumb.php

410 ms

timthumb.php

timthumb.php

672 ms

timthumb.php

timthumb.php

654 ms

timthumb.php

timthumb.php

725 ms

timthumb.php

timthumb.php

818 ms

timthumb.php

timthumb.php

743 ms

timthumb.php

timthumb.php

845 ms

VooDooprogramming.png

VooDooprogramming.png

805 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

579 ms

Accessibility Review

steko.am accessibility score

51

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.

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

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

Image elements do not have [alt] attributes

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

steko.am best practices score

75

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

steko.am SEO score

77

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

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

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

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

steko.am

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