Report Summary

  • 96

    Performance

    Renders faster than
    94% of other websites

  • 53

    Accessibility

    Visual factors better than
    that of 22% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 67

    SEO

    Google-friendlier than
    26% of websites

print.am

Print.am - տպագրական ծառայություններ, տպագրություն, կորպորատիվ նվերներ

Page Load Speed

1.1 sec in total

First Response

338 ms

Resources Loaded

636 ms

Page Rendered

120 ms

print.am screenshot

About Website

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

Տպագրում և պատրաստում ենք բուկլետներ, օրացույցներ, բացիկներ, այցեքարտեր, բլանկներ, թղթապանակներ, գովազային պաստառներ, հրավիրատոմսեր, ծրարներ, թղթից փաթեթներ, ֆիրմային նոթատետրեր, սեղանի դրոշակներ, գրի...

Visit print.am

Key Findings

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

Performance Metrics

print.am performance score

96

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.9 s

86/100

10%

LCP (Largest Contentful Paint)

Value2.3 s

93/100

25%

SI (Speed Index)

Value2.3 s

98/100

10%

TBT (Total Blocking Time)

Value90 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0.009

100/100

15%

TTI (Time to Interactive)

Value2.2 s

99/100

10%

Network Requests Diagram

print.am

338 ms

style.css

69 ms

script.js

72 ms

urchin.js

7 ms

__utm.gif

9 ms

Our browser made a total of 26 requests to load all elements on the main page. We found that 92% of them (24 requests) were addressed to the original Print.am, 8% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (338 ms) belongs to the original domain Print.am.

Page Optimization Overview & Recommendations

Page size can be reduced by 22.1 kB (29%)

Content Size

77.2 kB

After Optimization

55.1 kB

In fact, the total size of Print.am main page is 77.2 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 15% of websites need less resources to load. Images take 43.9 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 16.1 kB

  • Original 19.8 kB
  • After minification 16.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 2.9 kB, which is 15% 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 16.1 kB or 81% of the original size.

Image Optimization

-0%

Potential reduce by 75 B

  • Original 43.9 kB
  • After minification 43.9 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. Print images are well optimized though.

JavaScript Optimization

-33%

Potential reduce by 3.5 kB

  • Original 10.5 kB
  • After minification 9.7 kB
  • After compression 7.0 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 3.5 kB or 33% of the original size.

CSS Optimization

-81%

Potential reduce by 2.4 kB

  • Original 2.9 kB
  • After minification 2.2 kB
  • After compression 565 B

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. Print.am needs all CSS files to be minified and compressed as it can save up to 2.4 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 5 (21%)

Requests Now

24

After Optimization

19

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

Accessibility Review

print.am accessibility score

53

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

High

Links do not have a discernible name

Best Practices

print.am best practices score

67

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

High

Browser errors were logged to the console

SEO Factors

print.am SEO score

67

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

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