Report Summary

  • 28

    Performance

    Renders faster than
    48% of other websites

  • 65

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

1in.am

1in.am

Page Load Speed

3.4 sec in total

First Response

463 ms

Resources Loaded

2.6 sec

Page Rendered

372 ms

1in.am screenshot

About Website

Click here to check amazing 1 In content for Armenia. Otherwise, check out these important facts you probably never knew about 1in.am

1in.am

Visit 1in.am

Key Findings

We analyzed 1in.am page load time and found that the first response time was 463 ms and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

1in.am performance score

28

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

59/100

10%

LCP (Largest Contentful Paint)

Value3.3 s

69/100

25%

SI (Speed Index)

Value11.1 s

6/100

10%

TBT (Total Blocking Time)

Value2,160 ms

6/100

30%

CLS (Cumulative Layout Shift)

Value0.532

14/100

15%

TTI (Time to Interactive)

Value15.4 s

7/100

10%

Network Requests Diagram

www.1in.am

463 ms

normalize.css

8 ms

main.css

184 ms

prettyPhoto.css

8 ms

datepicker.css

10 ms

Our browser made a total of 292 requests to load all elements on the main page. We found that 11% of them (31 requests) were addressed to the original 1in.am, 13% (37 requests) were made to Pic2.1in.am and 12% (36 requests) were made to Pic5.1in.am. The less responsive or slowest element that took the longest time to load (758 ms) relates to the external source Static.xx.fbcdn.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.4 MB (18%)

Content Size

7.8 MB

After Optimization

6.4 MB

In fact, the total size of 1in.am main page is 7.8 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. 85% 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 6.1 MB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 258.2 kB

  • Original 295.0 kB
  • After minification 239.6 kB
  • After compression 36.8 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 55.4 kB, which is 19% 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 258.2 kB or 88% of the original size.

Image Optimization

-2%

Potential reduce by 137.2 kB

  • Original 6.1 MB
  • After minification 5.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. 1 In images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 657.9 kB

  • Original 1.0 MB
  • After minification 1.0 MB
  • After compression 368.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 657.9 kB or 64% of the original size.

CSS Optimization

-83%

Potential reduce by 364.8 kB

  • Original 438.6 kB
  • After minification 400.4 kB
  • After compression 73.8 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. 1in.am needs all CSS files to be minified and compressed as it can save up to 364.8 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 63 (22%)

Requests Now

285

After Optimization

222

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

Accessibility Review

1in.am accessibility score

65

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

High

Links do not have a discernible name

Best Practices

1in.am best practices score

75

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

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

1in.am SEO score

75

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

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

    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 1in.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 1in.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

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