Tools & Wizards About Us
aes2.com screenshot

Report Summary

  • 32

    Performance

    Renders faster than
    52% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

aes2.com

Prophet 21 eCommerce Website Integration | P21 eCommerce | Prophet 21 Websites, P21 ECC/B2B Seller Alternative, e-Commerce Integration - B2B, B2C, P21...

Page Load Speed

3.8 sec in total

First Response

1.1 sec

Resources Loaded

2.3 sec

Page Rendered

439 ms

aes2.com screenshot

About Website

Visit aes2.com now to see the best up-to-date Aes 2 content for United States and also check out these interesting facts you probably never knew about aes2.com

Epicor Prophet21 ecommerce website integration. Superior alternative to P21 ECC or B2B Seller. P21, Acumatica, and TrulinX ecommerce websites and integration.

Visit aes2.com

Key Findings

We analyzed Aes2.com page load time and found that the first response time was 1.1 sec and then it took 2.8 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

aes2.com performance score

32

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

30/100

10%

LCP (Largest Contentful Paint)

Value6.4 s

10/100

25%

SI (Speed Index)

Value4.2 s

77/100

10%

TBT (Total Blocking Time)

Value1,900 ms

8/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value13.1 s

12/100

10%

Network Requests Diagram

www.aldrichsolutions.com

1069 ms

current.js

96 ms

bootstrap.min.css

65 ms

base_bundle.min.css

223 ms

home_bundle.min.css

189 ms

Our browser made a total of 44 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Aes2.com, 9% (4 requests) were made to Cdn.jsdelivr.net and 7% (3 requests) were made to Unpkg.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Aldrichsolutions.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 88.4 kB (35%)

Content Size

255.8 kB

After Optimization

167.3 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Aes2.com main page is 255.8 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. 50% of websites need less resources to load. Javascripts take 148.3 kB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 87.9 kB

  • Original 101.8 kB
  • After minification 71.7 kB
  • After compression 13.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 30.0 kB, which is 30% 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 87.9 kB or 86% of the original size.

Image Optimization

-4%

Potential reduce by 206 B

  • Original 5.7 kB
  • After minification 5.5 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. Aes 2 images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 254 B

  • Original 148.3 kB
  • After minification 148.3 kB
  • After compression 148.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. This website has mostly compressed JavaScripts.

Requests Breakdown

Number of requests can be reduced by 24 (59%)

Requests Now

41

After Optimization

17

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.aldrichsolutions.com

www.aldrichsolutions.com

1069 ms

current.js

current.js

96 ms

bootstrap.min.css

bootstrap.min.css

65 ms

base_bundle.min.css

base_bundle.min.css

223 ms

home_bundle.min.css

home_bundle.min.css

189 ms

wa_bundle.min.css

wa_bundle.min.css

185 ms

state.min.css

state.min.css

183 ms

custom.min.css

custom.min.css

174 ms

bootstrap-icons.css

bootstrap-icons.css

76 ms

fontawesome_bundle.min.css

fontawesome_bundle.min.css

213 ms

icon

icon

89 ms

jquery.min.js

jquery.min.js

119 ms

wa-scripts-callbacks-top.bundle.min.js

wa-scripts-callbacks-top.bundle.min.js

326 ms

plausible.js

plausible.js

131 ms

script.compat.js

script.compat.js

216 ms

nav.responsive.min.js

nav.responsive.min.js

351 ms

wa-scripts-shared.bundle.min.js

wa-scripts-shared.bundle.min.js

363 ms

wa-scripts-callbacks-bottom.bundle.min.js

wa-scripts-callbacks-bottom.bundle.min.js

472 ms

bootstrap.bundle.min.js

bootstrap.bundle.min.js

44 ms

jquery.validate.min.js

jquery.validate.min.js

87 ms

jquery.validate.unobtrusive.min.js

jquery.validate.unobtrusive.min.js

112 ms

jquery.unobtrusive-ajax.min.js

jquery.unobtrusive-ajax.min.js

429 ms

aos.js

aos.js

86 ms

gtm.js

gtm.js

94 ms

aos.css

aos.css

17 ms

aos.js

aos.js

17 ms

fbevents.js

fbevents.js

149 ms

af8f00d5-1ccd-4413-b541-d426d1e43ecf.png

af8f00d5-1ccd-4413-b541-d426d1e43ecf.png

334 ms

logo.png

logo.png

360 ms

bg_hero_2.webp

bg_hero_2.webp

508 ms

hp_col_block_1.webp

hp_col_block_1.webp

386 ms

hp_col_block_2.webp

hp_col_block_2.webp

387 ms

hp_cs_thumb.webp

hp_cs_thumb.webp

541 ms

logo_mastermans.webp

logo_mastermans.webp

423 ms

logo_austinhose.webp

logo_austinhose.webp

492 ms

logo_memco.webp

logo_memco.webp

528 ms

logo_alp.webp

logo_alp.webp

527 ms

logo_texcel.webp

logo_texcel.webp

591 ms

why_you_need_specialized_ecommerce.jpg

why_you_need_specialized_ecommerce.jpg

729 ms

weballiance_compare.webp

weballiance_compare.webp

665 ms

weballiance_virtual_tour.webp

weballiance_virtual_tour.webp

677 ms

c69950b8-ebc4-45e6-83cd-0db83caf676e.png

c69950b8-ebc4-45e6-83cd-0db83caf676e.png

408 ms

bootstrap-icons.woff

bootstrap-icons.woff

109 ms

print.min.css

print.min.css

45 ms

Accessibility Review

aes2.com accessibility score

85

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

[aria-*] attributes do not have valid values

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

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

Links do not have a discernible name

Best Practices

aes2.com best practices score

83

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

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

aes2.com SEO score

93

Search Engine Optimization Advices

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

    EN

  • Encoding

    UTF-8

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

aes2.com

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