3.7 sec in total
256 ms
2.4 sec
990 ms
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.comWe analyzed Aes2.com page load time and found that the first response time was 256 ms and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
aes2.com performance score
name
value
score
weighting
Value4.2 s
19/100
10%
Value5.8 s
15/100
25%
Value9.6 s
11/100
10%
Value16,170 ms
0/100
30%
Value0.079
94/100
15%
Value25.6 s
0/100
10%
256 ms
50 ms
138 ms
150 ms
104 ms
Our browser made a total of 81 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Aes2.com, 5% (4 requests) were made to Unpkg.com and 5% (4 requests) were made to Cdn.jsdelivr.net. The less responsive or slowest element that took the longest time to load (1.5 sec) relates to the external source Aldrichsolutions.com.
Page size can be reduced by 88.4 kB (24%)
372.9 kB
284.5 kB
In fact, the total size of Aes2.com main page is 372.9 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. 60% of websites need less resources to load. Images take 191.9 kB which makes up the majority of the site volume.
Potential reduce by 87.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 36.5 kB, which is 36% 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.2 kB or 86% of the original size.
Potential reduce by 878 B
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.
Potential reduce by 382 B
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.
Potential reduce by 0 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. Aes2.com has all CSS files already compressed.
Number of requests can be reduced by 31 (41%)
75
44
The browser has sent 75 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 22 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
www.aldrichsolutions.com
256 ms
css
50 ms
bootstrap.min.css
138 ms
bootstrap-icons.css
150 ms
fontawesome_bundle.min.css
104 ms
icon
62 ms
aldrichsolutions_v2_bundle.min.css
190 ms
custom.css
105 ms
jquery.min.js
43 ms
wa-scripts-callbacks-top.bundle.min.js
119 ms
plausible.js
40 ms
script.compat.js
39 ms
current.js
46 ms
home-page.bundle.min.js
122 ms
wa-scripts-callbacks-bottom.bundle.min.js
300 ms
bootstrap.bundle.min.js
151 ms
jquery.validate.min.js
54 ms
jquery.validate.unobtrusive.min.js
64 ms
jquery.unobtrusive-ajax.min.js
181 ms
aos.js
57 ms
aos.css
86 ms
aos.js
22 ms
aos.css
16 ms
e177c19b-5584-44c9-9185-1abf7594528d.png
621 ms
dc78041c-0352-429b-8b87-2fefdc0178e8.png
612 ms
logo.png
616 ms
m-logo-new.png
633 ms
slider_paint_no_dots4.jpg
634 ms
distributor_text2.png
634 ms
regional.png
633 ms
mastermans.png
633 ms
colker.png
789 ms
memco.png
1066 ms
virtual_tour.png
1067 ms
pulse-icon.png
1067 ms
store-icon.png
1066 ms
pim-checklist.png
1066 ms
mobile-app-icon.png
1202 ms
sell-small.png
1174 ms
care-small.png
1171 ms
site-traffic-small.png
1203 ms
ecomm-icon.png
1223 ms
price-down.png
1219 ms
more-arrows.png
1262 ms
understand2-sm.jpg
1265 ms
icon1.png
1275 ms
icon2.png
1310 ms
icon3.png
1310 ms
p21_integration2.png
1372 ms
logo.png
1383 ms
744343497
571 ms
bg_solutions.png
1352 ms
bg_cost4.jpg
1426 ms
checkmark_green.png
1351 ms
bg_numbers.jpg
1413 ms
bg_estimate2.jpg
1451 ms
fontawesome-webfont.woff
1511 ms
bootstrap-icons.woff
123 ms
gtm.js
489 ms
displaylogincallback
958 ms
getactivelocation
1026 ms
cartsummary
1027 ms
freeshippingsummary
1027 ms
1497408425-07e59fe7498483b9362c713d2032c32d326beb60d14e7c4acb0c686eafef385d-d.jpg
37 ms
player.js
239 ms
player.css
143 ms
vuid.min.js
173 ms
analytics.js
385 ms
2966055.js
339 ms
js
61 ms
1497408425-07e59fe7498483b9362c713d2032c32d326beb60d14e7c4acb0c686eafef385d-d
456 ms
leadflows.js
100 ms
collectedforms.js
95 ms
2966055.js
86 ms
conversations-embed.js
99 ms
2966055.js
146 ms
fb.js
93 ms
collect
63 ms
collect
30 ms
print.min.css
62 ms
print.css
44 ms
aes2.com accessibility score
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
[aria-*] attributes do not have valid values
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
Buttons do not have an accessible name
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
Heading elements are not in a sequentially-descending order
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
aes2.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
aes2.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
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
Document uses legible font sizes
EN
EN
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.
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: