Report Summary

  • 45

    Performance

    Renders faster than
    64% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

aviny.com

| موسسه فرهنگی هنری اندیشه شهید آوینی

Page Load Speed

11.9 sec in total

First Response

590 ms

Resources Loaded

10.9 sec

Page Rendered

419 ms

About Website

Visit aviny.com now to see the best up-to-date Aviny content for Iran and also check out these interesting facts you probably never knew about aviny.com

Visit aviny.com

Key Findings

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

Performance Metrics

aviny.com performance score

45

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

74/100

10%

LCP (Largest Contentful Paint)

Value4.9 s

29/100

25%

SI (Speed Index)

Value6.0 s

47/100

10%

TBT (Total Blocking Time)

Value710 ms

41/100

30%

CLS (Cumulative Layout Shift)

Value0.322

36/100

15%

TTI (Time to Interactive)

Value4.9 s

78/100

10%

Network Requests Diagram

aviny.com

590 ms

aviny.com

721 ms

www.aviny.com

1241 ms

css_zVGYEub7CB7oQGePRgmnTIIs2q6ht0XxgV7yOhBghXA.css

188 ms

css_v19HUOxzmyWYBGPjMd2XLuls9hMcqS9mKT-nCnF4X-0.css

557 ms

Our browser made a total of 74 requests to load all elements on the main page. We found that 97% of them (72 requests) were addressed to the original Aviny.com, 3% (2 requests) were made to Stat.aviny.com. The less responsive or slowest element that took the longest time to load (7.8 sec) belongs to the original domain Aviny.com.

Page Optimization Overview & Recommendations

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

Content Size

2.8 MB

After Optimization

2.5 MB

In fact, the total size of Aviny.com main page is 2.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. 60% of websites need less resources to load. Images take 2.4 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 60.2 kB

  • Original 71.4 kB
  • After minification 66.5 kB
  • After compression 11.3 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 60.2 kB or 84% of the original size.

Image Optimization

-8%

Potential reduce by 196.0 kB

  • Original 2.4 MB
  • After minification 2.2 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. Aviny images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 0 B

  • Original 235.6 kB
  • After minification 235.6 kB
  • After compression 235.6 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

-0%

Potential reduce by 63 B

  • Original 43.6 kB
  • After minification 43.6 kB
  • After compression 43.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. Aviny.com has all CSS files already compressed.

Requests Breakdown

We found no issues to fix!

Requests Now

58

After Optimization

58

The browser has sent 58 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Aviny. According to our analytics all requests are already optimized.

Accessibility Review

aviny.com accessibility score

75

Accessibility Issues

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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.

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

ARIA IDs are not unique

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

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

High

Missing source maps for large first-party JavaScript

SEO Factors

aviny.com SEO score

79

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

Language and Encoding

  • Language Detected

    FA

  • Language Claimed

    FA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Aviny.com can be misinterpreted by Google and other search engines. Our service has detected that Persian is used on the page, and it matches the claimed language. Our system also found out that Aviny.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 description is not detected on the main page of Aviny. 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: