Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 74% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

shtigen.com

Վերակագնվող և Արևային էներգիայի Լուծումներ | SHTIGEN

Page Load Speed

3.7 sec in total

First Response

263 ms

Resources Loaded

2.7 sec

Page Rendered

791 ms

About Website

Click here to check amazing SHTIGEN content for Armenia. Otherwise, check out these important facts you probably never knew about shtigen.com

Շտիգենը առաջարկում է ստանալ անվճար տաք ջուր և էլեկտրաէներգիա՝ արևային պանելների և ջրատաքացուցիչների միջոցով։ արևային վահանակների տեղադրում ՀՀ-ում և ԼՂՀ-ում։

Visit shtigen.com

Key Findings

We analyzed Shtigen.com page load time and found that the first response time was 263 ms and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

shtigen.com performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

31/100

10%

LCP (Largest Contentful Paint)

Value14.7 s

0/100

25%

SI (Speed Index)

Value11.9 s

4/100

10%

TBT (Total Blocking Time)

Value880 ms

32/100

30%

CLS (Cumulative Layout Shift)

Value0.555

13/100

15%

TTI (Time to Interactive)

Value14.9 s

8/100

10%

Network Requests Diagram

shtigen.com

263 ms

552 ms

bootstrap.min.css

129 ms

blog.css

31 ms

brand-slider.css

25 ms

Our browser made a total of 92 requests to load all elements on the main page. We found that 67% of them (62 requests) were addressed to the original Shtigen.com, 13% (12 requests) were made to Fonts.gstatic.com and 11% (10 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Shtigen.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 560.9 kB (9%)

Content Size

6.3 MB

After Optimization

5.7 MB

In fact, the total size of Shtigen.com main page is 6.3 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 5.6 MB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 160.4 kB

  • Original 209.8 kB
  • After minification 200.7 kB
  • After compression 49.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 160.4 kB or 76% of the original size.

Image Optimization

-6%

Potential reduce by 361.6 kB

  • Original 5.6 MB
  • After minification 5.3 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. SHTIGEN images are well optimized though.

JavaScript Optimization

-9%

Potential reduce by 31.9 kB

  • Original 348.7 kB
  • After minification 348.7 kB
  • After compression 316.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. This website has mostly compressed JavaScripts.

CSS Optimization

-6%

Potential reduce by 7.0 kB

  • Original 109.5 kB
  • After minification 109.4 kB
  • After compression 102.5 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. Shtigen.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 62 (84%)

Requests Now

74

After Optimization

12

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

Accessibility Review

shtigen.com accessibility score

90

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

shtigen.com 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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

shtigen.com SEO score

91

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    HY

  • Language Claimed

    HY

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Shtigen.com can be misinterpreted by Google and other search engines. Our service has detected that Armenian is used on the page, and it matches the claimed language. Our system also found out that Shtigen.com 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 SHTIGEN. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: