Tools & Wizards About Us
atrex.com screenshot

Report Summary

  • 87

    Performance

    Renders faster than
    89% of other websites

  • 42

    Accessibility

    Visual factors better than
    that of 19% of websites

  • 50

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

atrex.com

Atrex Inventory Control/Point of Sale - Millennium Software, Inc.

Page Load Speed

765 ms in total

First Response

120 ms

Resources Loaded

504 ms

Page Rendered

141 ms

atrex.com screenshot

About Website

Welcome to atrex.com homepage info - get ready to check Atrex best content right away, or after learning these important things about atrex.com

Millennium Software Inc. Developer of Atrex Inventory Control / Point of Sale Software.

Visit atrex.com

Key Findings

We analyzed Atrex.com page load time and found that the first response time was 120 ms and then it took 645 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 10% of websites can load faster.

Performance Metrics

atrex.com performance score

87

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.7 s

91/100

10%

LCP (Largest Contentful Paint)

Value2.0 s

97/100

25%

SI (Speed Index)

Value1.7 s

100/100

10%

TBT (Total Blocking Time)

Value10 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.423

23/100

15%

TTI (Time to Interactive)

Value2.0 s

99/100

10%

Network Requests Diagram

atrex.com

120 ms

atrex.com

120 ms

style.css

31 ms

respon.css

64 ms

jquery-1.7.2.min.js

120 ms

Our browser made a total of 28 requests to load all elements on the main page. We found that 96% of them (27 requests) were addressed to the original Atrex.com, 4% (1 request) were made to Seal.beyondsecurity.com. The less responsive or slowest element that took the longest time to load (163 ms) belongs to the original domain Atrex.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 144.0 kB (40%)

Content Size

364.6 kB

After Optimization

220.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Atrex.com main page is 364.6 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. 20% of websites need less resources to load. Images take 173.2 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 9.8 kB

  • Original 13.0 kB
  • After minification 10.3 kB
  • After compression 3.2 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.7 kB, which is 21% 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 9.8 kB or 76% of the original size.

Image Optimization

-3%

Potential reduce by 5.6 kB

  • Original 173.2 kB
  • After minification 167.6 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. Atrex images are well optimized though.

JavaScript Optimization

-70%

Potential reduce by 102.5 kB

  • Original 146.0 kB
  • After minification 123.5 kB
  • After compression 43.5 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 102.5 kB or 70% of the original size.

CSS Optimization

-80%

Potential reduce by 26.0 kB

  • Original 32.4 kB
  • After minification 24.7 kB
  • After compression 6.3 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. Atrex.com needs all CSS files to be minified and compressed as it can save up to 26.0 kB or 80% of the original size.

Requests Breakdown

Number of requests can be reduced by 13 (52%)

Requests Now

25

After Optimization

12

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

atrex.com

atrex.com

120 ms

atrex.com

atrex.com

120 ms

style.css

style.css

31 ms

respon.css

respon.css

64 ms

jquery-1.7.2.min.js

jquery-1.7.2.min.js

120 ms

scripts.js

scripts.js

107 ms

feature-carousel.css

feature-carousel.css

108 ms

jquery.easing.js

jquery.easing.js

114 ms

jquery.featureCarousel.js

jquery.featureCarousel.js

149 ms

superfish.css

superfish.css

132 ms

hoverIntent.js

hoverIntent.js

134 ms

superfish.js

superfish.js

135 ms

supersubs.js

supersubs.js

143 ms

selectnav.min.js

selectnav.min.js

147 ms

website.css

website.css

153 ms

jquery.tinycarousel.min.js

jquery.tinycarousel.min.js

161 ms

menu_html_block.js

menu_html_block.js

163 ms

vulnerability-scanner-2.gif

vulnerability-scanner-2.gif

40 ms

main_bg.png

main_bg.png

40 ms

ms300.gif

ms300.gif

42 ms

image2.png

image2.png

40 ms

image1.png

image1.png

54 ms

image3.png

image3.png

59 ms

ul_li_menu_a.png

ul_li_menu_a.png

28 ms

arrow-l.png

arrow-l.png

32 ms

arrow-r.png

arrow-r.png

28 ms

prefooter_bg.png

prefooter_bg.png

30 ms

footer_bg.png

footer_bg.png

45 ms

Accessibility Review

atrex.com accessibility score

42

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

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

atrex.com best practices score

50

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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

atrex.com SEO score

85

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

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Atrex.com can be misinterpreted by Google and other search engines. Our service has detected that English 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 Atrex.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

atrex.com

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