1.5 sec in total
72 ms
935 ms
520 ms
Visit aequus.us now to see the best up-to-date Aequus content and also check out these interesting facts you probably never knew about aequus.us
Boost your business with Aequus Worldwide, top U.S. global supply chain & logistics company specializing in 3PL, freight forwarding, customs
Visit aequus.usWe analyzed Aequus.us page load time and found that the first response time was 72 ms and then it took 1.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.
aequus.us performance score
name
value
score
weighting
Value2.9 s
53/100
10%
Value5.5 s
19/100
25%
Value2.9 s
95/100
10%
Value140 ms
95/100
30%
Value0.08
94/100
15%
Value4.9 s
77/100
10%
72 ms
32 ms
249 ms
337 ms
107 ms
Our browser made a total of 100 requests to load all elements on the main page. We found that 15% of them (15 requests) were addressed to the original Aequus.us, 74% (74 requests) were made to Hb.wpmucdn.com and 5% (5 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (526 ms) relates to the external source Hb.wpmucdn.com.
Page size can be reduced by 178.5 kB (22%)
794.9 kB
616.4 kB
In fact, the total size of Aequus.us main page is 794.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. 55% of websites need less resources to load. Javascripts take 392.9 kB which makes up the majority of the site volume.
Potential reduce by 172.5 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 172.5 kB or 83% of the original size.
Potential reduce by 11 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. Obviously, Aequus needs image optimization as it can save up to 11 B or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 4.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. This website has mostly compressed JavaScripts.
Potential reduce by 1.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. Aequus.us has all CSS files already compressed.
Number of requests can be reduced by 82 (94%)
87
5
The browser has sent 87 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Aequus. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 77 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
aequus.us
72 ms
aequus.us
32 ms
7cb219b2-8186-4da5-bfc0-13c709a88032.css
249 ms
c71ba4d7-9ac5-4861-88ed-3f3a7689103a.css
337 ms
a480a909-87c7-48cb-9d26-33630a6d3773.js
107 ms
b419bfb9-601a-4cbd-b317-6d52b1574c16.js
87 ms
8173dac7-c21c-428f-bfdc-3ac4cfca8896.js
83 ms
js
92 ms
js
152 ms
swap.js
71 ms
css
72 ms
font-awesome.css
44 ms
pe-icon-7-stroke.css
54 ms
734f2028-6fad-4c14-9e3c-27d2bb69f14b.css
265 ms
ae00463c-d1cd-42f2-b375-8eaeabe3d05e.css
284 ms
3522d3c4-485e-4292-9b8f-222b3b37b782.js
112 ms
fcfee309-fbae-46fb-b387-ca05af349d74.js
138 ms
be6bc635-10a9-4de3-ad28-955c056f6eaf.js
150 ms
ce07a961-6d9c-44a0-9b6a-392cca3ff88f.js
193 ms
70d18dbb-7146-47fb-9f0f-96ba1dafcfef.js
184 ms
9611a2dc-c7ba-4fe5-9be0-083655a03310.js
263 ms
e729fc4f-55dc-4116-91bc-301be733b68d.js
243 ms
97db532e-04a9-4d76-b010-c8362bb7f839.js
246 ms
d4559039-0558-43fe-95ec-2b8acf2d4843.js
268 ms
de275077-49ab-4fd4-af70-66909c7492e6.js
283 ms
116277.js
89 ms
1c431281-1dd5-48ec-aabd-661dfd296496.js
297 ms
api.js
75 ms
wp-polyfill.min.js
52 ms
ebc403f6-900e-4e76-a1c6-9ccbcf76ae2a.js
304 ms
469e384d-d10c-4fac-9878-586de0612739.js
512 ms
6aac9019-81d1-4e15-b3d9-d5cf948e9279.js
514 ms
68080106-1265-49aa-b023-4cbedb45cc1c.js
319 ms
fdf83310-10b4-4510-ab02-515d16d66bb6.js
513 ms
650caa42-0ced-45a6-831f-d28c9c9e477d.js
510 ms
c6fb8086-27bb-42f3-a724-3aaae1197efb.js
515 ms
e8bd6a06-9ee3-4a37-b4b4-0308244cacba.js
515 ms
43bc3d25-16ed-4b48-96a8-4e17019d33a0.js
517 ms
02b00aaf-f160-45f1-a543-ef1ac76bb736.js
515 ms
6f4c0c2e-7d4f-40a1-b06d-e66e9355b486.js
524 ms
c7bd3b54-7e57-41c2-8732-dc33bc7c9eb3.js
517 ms
f88e6681-b321-40bc-a0c4-c4f0cd6e8e0f.js
520 ms
be6c5d90-8615-45bc-88fc-caccb74cee44.js
521 ms
696f79fc-46b0-43c9-bfc6-af345024d72b.js
518 ms
42dabd70-2d29-48dc-a8c8-85321182ddaf.js
526 ms
3d8f0f71-4ac1-4ffe-a69d-27b196903c3a.js
522 ms
fd5cda6c-644b-4144-8177-1436bd2a69f8.js
523 ms
fusion-flexslider.js
47 ms
fusion-animations.js
48 ms
5e6d1286-52da-4244-9104-b5f05d577951.js
449 ms
8d5e7f76-0e4a-4c9d-95e4-9fac99004216.js
446 ms
fa94e7b5-d223-47e4-8230-5422fe9ac5d6.js
430 ms
ce7f442e-748a-478e-81d6-172359362a58.js
418 ms
95ed5704-4d52-4857-b3a8-1aa88408701f.js
393 ms
5331b86d-133a-4a49-94b8-05b479a4be39.js
381 ms
1c89e9d2-b11f-4be3-b53f-efae84e1324e.js
348 ms
44d12c4c-9030-4852-a82d-5aa8a2559d58.js
376 ms
c3fe1964-afcd-4b27-94ff-84dbb5c3ce7f.js
324 ms
76e76096-05fb-4bcf-af4d-45b8b57cc990.js
288 ms
1191d0f3-509d-4d57-b210-b0abc4fcfebf.js
322 ms
c2e657dd-7717-4738-86b9-085341c12d1b.js
269 ms
dc087e80-38e2-466e-a6ed-e8840df59487.js
303 ms
e6537de0-b953-4620-a74f-ca806393e6e8.js
296 ms
1e4d08bf-6a7f-43d6-a9fa-bc2a045f1860.js
286 ms
3f2e1ba4-55fc-4449-939d-d7221f5acc70.js
341 ms
19ea093f-51f5-4fdd-8aff-69f2fd63eb28.js
328 ms
f5e141e5-b389-4719-8409-56874a75302d.js
322 ms
b22002aa-2879-40d5-b5a8-4c028310060f.js
250 ms
dummy.png
124 ms
AEQUUS-Top-Content-Background-1024x701-1-300x205.webp
53 ms
AEQUUS-Bottom-Content-279x300.webp
52 ms
f89b4948-8ec8-4df8-aaa7-e7cb79e2f585.js
58 ms
1af34a0e-0711-42ed-b0f5-6e7ebdf80610.js
110 ms
de060daa-f49f-4585-a814-aa4bd945871e.js
112 ms
671d56f5-14d6-4c79-bc61-8d5e6cd2ab63.js
110 ms
0dd4dd28-e8a4-4c4c-819b-372898ebd8d8.js
110 ms
04d20f95-06c1-4d3d-b69c-6476889c3d15.js
111 ms
7be1990a-07b0-440a-9e4b-38f39b1eeb80.js
274 ms
149adc38-c7c2-4d36-b6b4-d7d29facf8bd.js
142 ms
7c032666-fa0f-41af-ac08-81ef6917148c.js
240 ms
75b8aa5a-6eaa-4b3c-912b-002a16aa2e10.js
239 ms
82fa3605-f6b7-4fa7-a689-052919047b88.js
239 ms
fded1481-7597-495a-88bf-420e5a6efdf9.js
136 ms
fcf5c685-c0d9-46d6-88c6-a834e10e9f56.js
236 ms
fefbfc0c-1061-4bf3-9250-4f13e516bac6.js
265 ms
a91aa3f9-9829-49b1-b3ae-6868ec403f77.js
265 ms
161b46d3-a007-4e7c-adb2-911497b0619b.js
264 ms
48e9bc58-b6e9-4318-8484-3d77a1e21345.js
263 ms
703221c7-1550-4283-b421-f9adc6fa1d6e.js
262 ms
f8b2bea7-98a8-4756-ba4a-6ec447e1bab0.js
305 ms
awb-icons.woff
34 ms
fa-solid-900.woff
33 ms
fa-regular-400.woff
163 ms
QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K0nXBi8Jow.ttf
133 ms
QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K3vXBi8Jow.ttf
163 ms
QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32KxfXBi8Jow.ttf
173 ms
QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K5fQBi8Jow.ttf
173 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf
174 ms
Pe-icon-7-stroke.woff
100 ms
fontawesome-webfont.woff
15 ms
aequus.us accessibility score
aequus.us best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
aequus.us SEO score
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 Aequus.us 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 Aequus.us 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.
aequus.us
Open Graph data is detected on the main page of Aequus. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: