2.4 sec in total
13 ms
1.8 sec
598 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
Aequus offers full-service commercial freight forwarding. Get 24-hour customs broker services. We are your Trusted Logistics Partner!
Visit aequus.usWe analyzed Aequus.us page load time and found that the first response time was 13 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
aequus.us performance score
name
value
score
weighting
Value2.9 s
54/100
10%
Value5.4 s
20/100
25%
Value2.9 s
95/100
10%
Value200 ms
90/100
30%
Value0.022
100/100
15%
Value4.9 s
78/100
10%
13 ms
38 ms
106 ms
358 ms
65 ms
Our browser made a total of 102 requests to load all elements on the main page. We found that 15% of them (15 requests) were addressed to the original Aequus.us, 75% (76 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 (1.1 sec) relates to the external source Hb.wpmucdn.com.
Page size can be reduced by 275.7 kB (30%)
922.1 kB
646.5 kB
In fact, the total size of Aequus.us main page is 922.1 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 480.3 kB which makes up the majority of the site volume.
Potential reduce by 170.9 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 170.9 kB or 82% 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 62.2 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 62.2 kB or 13% of the original size.
Potential reduce by 42.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 needs all CSS files to be minified and compressed as it can save up to 42.5 kB or 18% of the original size.
Number of requests can be reduced by 84 (94%)
89
5
The browser has sent 89 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 79 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
aequus.us
13 ms
aequus.us
38 ms
cd334dea-f26d-4ea2-ab53-2ce24a6a203d.css
106 ms
c7741b81-3b3c-4a40-8164-b05116ba05c4.css
358 ms
7dab53ec-9065-42e5-bf24-52cbbdda61b2.js
65 ms
4d3376b9-193f-4cb5-9698-fd26b7cdafed.js
101 ms
fb4a4861-baa1-48d8-813c-cc34a4607b0b.js
107 ms
js
110 ms
js
163 ms
swap.js
72 ms
css
70 ms
font-awesome.css
43 ms
pe-icon-7-stroke.css
56 ms
cb5ff335-63c1-4762-8805-dc9821ad681e.css
199 ms
577d1982-50c8-45f8-9a72-95c895515b74.css
199 ms
eff6da24-24a2-4926-8ca7-152673185107.js
230 ms
629412d7-bf52-4c09-b4f6-1124558715c1.js
254 ms
a6ac445a-beaa-4de3-b536-cf3c101ae522.js
626 ms
2dde9ec9-f812-4d8c-a567-1728ecdbe17e.js
960 ms
fa4ef659-994f-4c2e-b3f6-ae36b63d3721.js
200 ms
4add086e-62b2-4758-8af5-1009a72effec.js
288 ms
c7ad14d8-2d72-4d88-bb51-bc1cceb3f494.js
516 ms
7ef97a64-98e5-459e-b269-a24263b3d542.js
517 ms
3b7409c5-35f6-4a8d-8ea1-07a8868c06ec.js
519 ms
823603ca-e89f-4d2c-af93-74a2ee0ebf0c.js
517 ms
116277.js
89 ms
a0fa201b-8ecf-4002-9711-04183d0c4f87.js
520 ms
api.js
80 ms
7f86b493-4aa1-43cd-ba7b-b49d1c1eaad6.js
518 ms
6d751a3c-1c39-4181-8162-b8c3bcd9f15c.js
558 ms
wp-polyfill.min.js
59 ms
dc82a165-5f1b-47dc-acf1-15b9f2a76b7a.js
788 ms
ce95e22c-3367-47cf-8fd1-f34154a2bf16.js
520 ms
ff6d8b87-de3a-4d6d-a3f0-47a49e1c0c9f.js
619 ms
51cb55ad-d078-41ce-8ab0-0f8a261e93a8.js
786 ms
2cd7b50a-d5ca-4bc4-8584-6cb43fece7f7.js
620 ms
7364eba1-dc66-47bb-8fdc-23a9084cac07.js
829 ms
a73d1fa6-7283-4a93-a7a3-c82c9bcdd717.js
829 ms
8e446501-b44c-4395-aced-fb0b36b08a95.js
828 ms
4d5d08f5-568e-431c-8615-484bf8e89867.js
828 ms
65a2069d-362f-4c7a-a317-ee99aae22044.js
870 ms
3991b353-aaf1-419d-bf0f-ad4031a7e24d.js
868 ms
1d17b4de-c8b1-4338-9806-252078ff8f53.js
1000 ms
0d1f91aa-748d-4855-ad01-fd9c80b08eda.js
923 ms
3d0aea55-ef1c-45a2-a2a2-45a30b3722cd.js
1031 ms
6bf6f6cc-f271-4e55-8a1e-b4b2ee735f4d.js
944 ms
63d001bd-1e8d-4fac-bff5-3f49ac456392.js
974 ms
fusion-flexslider.js
51 ms
fusion-animations.js
49 ms
5eaffa65-91eb-4e12-8d86-11e26b356350.js
959 ms
879795e3-aeeb-4584-a1cc-e87cb3b011cc.js
964 ms
2a2c890b-a213-4ee7-81d7-3090464e31f8.js
1057 ms
c667538f-be22-446d-a144-02d62816513f.js
981 ms
819be86d-ea3f-430b-9f65-e733146a7830.js
879 ms
6d9515b7-7833-4af9-88ce-88b7842dc148.js
950 ms
5b1c296e-aa35-4bb6-bb5e-9ae5d17279f9.js
920 ms
a6df21e0-3cb9-4acf-bbc7-f400b5e3d005.js
968 ms
51d892af-9eef-46df-a90a-29870e5e5d46.js
892 ms
d45fa46e-bcb9-49cd-aacb-55e42b20bae1.js
1034 ms
dummy.png
113 ms
AEQUUS-Top-Content-Background-1024x701-1-300x205.webp
43 ms
AEQUUS-Bottom-Content-279x300.webp
43 ms
7e8c6c2e-4707-49d0-81fc-eac06c7f30a8.js
665 ms
2421b3f7-e9ba-4b11-a7a9-9cea06fb55e0.js
764 ms
60d202bb-98fa-4001-b14d-2f5d70470d23.js
771 ms
227d0a9c-7a88-48e7-b137-93432fa558d4.js
682 ms
791e5f4f-4f8d-4e53-b73e-ad4b5b593fea.js
740 ms
215cef72-6bb1-4eca-af7e-3cb5e13cda8b.js
745 ms
10f13eeb-8eb3-45a2-bc46-e5c40a00926c.js
798 ms
awb-icons.woff
38 ms
7457dba1-7ce1-47eb-8e4f-e6110029d206.js
851 ms
d4bb6e14-4a4b-49c2-911e-a6ee7ccb631c.js
669 ms
e42952a0-b6bf-472e-acea-c831a0d75b82.js
704 ms
3ab48f1b-c441-46a9-a6ad-5c27d28e05a0.js
752 ms
fa-solid-900.woff
46 ms
fa-regular-400.woff
209 ms
QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K0nXBi8Jow.ttf
166 ms
QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K3vXBi8Jow.ttf
167 ms
QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32KxfXBi8Jow.ttf
194 ms
QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K5fQBi8Jow.ttf
209 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf
208 ms
fbe27a94-690f-474d-b660-57352c04fb44.js
744 ms
Pe-icon-7-stroke.woff
122 ms
dd1d9248-1e62-499f-803b-8b8c1e693899.js
618 ms
e88bcede-b88e-4ec5-b535-cf055c637fa8.js
625 ms
fontawesome-webfont.woff
74 ms
0ddf9a33-0aff-4f9b-8a74-1a314d41d1ba.js
591 ms
43e445b9-494c-454f-93fe-78bbf465f3c7.js
676 ms
7629b6f8-9728-4d61-853a-bd062edea83e.js
615 ms
64ab35ed-33f2-48d3-95e5-065aeb140c62.js
630 ms
cb7c2a5a-4ebb-48ee-a9d8-ea4571fcb737.js
570 ms
838c1bc6-2870-417a-84d6-4d9bb868201c.js
742 ms
2f956ad2-c542-4803-97df-8ea96b6c5b19.js
496 ms
74f7bb78-dbb6-4269-a0b9-ae6e034caf36.js
614 ms
2b8f2651-3e83-4a44-a3e4-15a577d4abfe.js
617 ms
b0691ed9-c7bb-48ad-8d7c-ec1c010de2de.js
701 ms
af6e0243-f721-4ca7-b4a7-f5ba92e2dc18.js
688 ms
95704fec-79a0-46c1-846e-ad5859997a70.js
597 ms
e4e3771d-1b7b-4288-bb52-9215b92986ec.js
672 ms
f2d75251-5ca0-46ed-843e-2eb136b533ac.js
642 ms
b46fa125-959c-4221-9d00-6840987323de.js
568 ms
7463cbf6-0759-4958-ad7f-81d468d1f784.js
614 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: