Report Summary

  • 49

    Performance

    Renders faster than
    68% of other websites

  • 72

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 68

    SEO

    Google-friendlier than
    28% of websites

azarius.net

Azarius - Azarius

Page Load Speed

2.8 sec in total

First Response

590 ms

Resources Loaded

2.1 sec

Page Rendered

178 ms

azarius.net screenshot

About Website

Click here to check amazing Azarius content for United States. Otherwise, check out these important facts you probably never knew about azarius.net

Psychedelics & Cannabis News | Since 1999 - Azarius

Visit azarius.net

Key Findings

We analyzed Azarius.net page load time and found that the first response time was 590 ms and then it took 2.2 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

azarius.net performance score

49

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

61/100

10%

LCP (Largest Contentful Paint)

Value9.1 s

1/100

25%

SI (Speed Index)

Value6.1 s

45/100

10%

TBT (Total Blocking Time)

Value460 ms

62/100

30%

CLS (Cumulative Layout Shift)

Value0.014

100/100

15%

TTI (Time to Interactive)

Value7.2 s

50/100

10%

Network Requests Diagram

azarius.net

590 ms

style-1456739322.css

377 ms

logo-azarius.png

342 ms

02-2016-After-D-UK.jpg

861 ms

02-2016-hipVap-UK.jpg

906 ms

Our browser made a total of 50 requests to load all elements on the main page. We found that 44% of them (22 requests) were addressed to the original Azarius.net, 14% (7 requests) were made to Apis.google.com and 6% (3 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Azarius.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 652.5 kB (22%)

Content Size

3.0 MB

After Optimization

2.3 MB

In fact, the total size of Azarius.net main page is 3.0 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. 45% of websites need less resources to load. Images take 2.3 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 47.6 kB

  • Original 60.9 kB
  • After minification 52.2 kB
  • After compression 13.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. This page needs HTML code to be minified as it can gain 8.7 kB, which is 14% 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 47.6 kB or 78% of the original size.

Image Optimization

-3%

Potential reduce by 76.7 kB

  • Original 2.3 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. Azarius images are well optimized though.

JavaScript Optimization

-61%

Potential reduce by 44.7 kB

  • Original 73.6 kB
  • After minification 73.6 kB
  • After compression 28.9 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 44.7 kB or 61% of the original size.

CSS Optimization

-87%

Potential reduce by 483.5 kB

  • Original 555.3 kB
  • After minification 553.9 kB
  • After compression 71.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. Azarius.net needs all CSS files to be minified and compressed as it can save up to 483.5 kB or 87% of the original size.

Requests Breakdown

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

Requests Now

48

After Optimization

28

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

Accessibility Review

azarius.net accessibility score

72

Accessibility Issues

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

button, link, and menuitem elements do not have accessible names.

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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.

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

azarius.net best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

azarius.net SEO score

68

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

Links do not have descriptive text

High

Image elements do not have [alt] attributes

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

    EN

  • Language Claimed

    UK

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Azarius.net can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Ukrainian language. Our system also found out that Azarius.net main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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