1.8 sec in total
129 ms
1.3 sec
354 ms
Visit aftership.com now to see the best up-to-date After Ship content for United States and also check out these interesting facts you probably never knew about aftership.com
AfterShip pioneers how brands improve customer loyalty through automated shipping, branded order tracking, proactive messaging, and seamless returns experiences.
Visit aftership.comWe analyzed Aftership.com page load time and found that the first response time was 129 ms and then it took 1.7 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.
aftership.com performance score
name
value
score
weighting
Value3.7 s
30/100
10%
Value4.9 s
28/100
25%
Value4.5 s
71/100
10%
Value150 ms
94/100
30%
Value0.062
97/100
15%
Value10.3 s
24/100
10%
129 ms
7 ms
16 ms
29 ms
39 ms
Our browser made a total of 85 requests to load all elements on the main page. We found that 44% of them (37 requests) were addressed to the original Aftership.com, 12% (10 requests) were made to Track.aftership.com and 9% (8 requests) were made to Button.aftership.com. The less responsive or slowest element that took the longest time to load (368 ms) relates to the external source S.ytimg.com.
Page size can be reduced by 659.2 kB (43%)
1.5 MB
879.2 kB
In fact, the total size of Aftership.com main page is 1.5 MB. 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. Javascripts take 665.5 kB which makes up the majority of the site volume.
Potential reduce by 11.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. 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 11.8 kB or 74% of the original size.
Potential reduce by 886 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. After Ship images are well optimized though.
Potential reduce by 352.8 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 352.8 kB or 53% of the original size.
Potential reduce by 293.8 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. Aftership.com needs all CSS files to be minified and compressed as it can save up to 293.8 kB or 82% of the original size.
Number of requests can be reduced by 43 (59%)
73
30
The browser has sent 73 CSS, Javascripts, AJAX and image requests in order to completely render the main page of After Ship. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
www.aftership.com
129 ms
bootstrap.min.css
7 ms
font-awesome-493fd2230c23ef25d39b2cb0df6e5d14.css
16 ms
style-bc6b495c8ba7e1f9607f41dc57602cc3.css
29 ms
jquery.min.js
39 ms
bootstrap.min.js
52 ms
common-4d9091e542ad91e51dae694fb69afc3e.js
51 ms
jquery.ban.css
27 ms
jquery.ban.js
59 ms
setup_home-95bd92fa492c98b5140170d59116c8d1.js
58 ms
logo-aftership-light.svg
6 ms
shopify.png
11 ms
ebay.png
10 ms
magento.png
7 ms
bigcommerce.png
8 ms
aftership-ios-app.png
9 ms
aftership-android-app.png
13 ms
track_analytics_1.png
11 ms
track_analytics_2.png
14 ms
home_video_thumb.png
15 ms
home-avatar.png
11 ms
tshirt.png
16 ms
bar.png
13 ms
diamond.png
13 ms
aftershipios1.png
17 ms
aftershipios2.png
18 ms
aftershipios3.png
18 ms
aftershipios4.png
15 ms
aftershipios5.png
37 ms
all.js
299 ms
qIIYRU-oROkIk8vfvxw6QvesZW2xOQ-xsNqO47m55DA.woff
8 ms
kcf5uOXucLcbFOydGU24WALUuEpTyoUstqEm5AMlJo4.woff
12 ms
Kom15zUm24dIPfIRiNogNuvvDin1pK8aKteLpeZ5c0A.woff
50 ms
qdgUG4U09HnJwhYI-uK18wLUuEpTyoUstqEm5AMlJo4.woff
16 ms
status_icon_active.png
23 ms
DMZcVwy2K4s
132 ms
RC488201028HK
198 ms
status_icon.png
32 ms
envelop.png
39 ms
fontawesome-webfont.woff
34 ms
analytics.js
84 ms
button_widget.html
237 ms
button_widget.html
267 ms
button_widget.html
236 ms
button_widget.html
237 ms
collect
12 ms
www-embed-player-vflQrT_sR.css
145 ms
www-embed-player.js
246 ms
base.js
368 ms
styles-334d1387f5dee1f9f62d8575733ffc28.css
29 ms
style-bd683ec66357376ee2d114464ca5eafb.css
182 ms
modernizr-2.7.1-respond-1.4.2.min-2521cee107498c65e4186461f3f4e04a.js
75 ms
jquery.min.js
228 ms
bootstrap.min-e289e4c64ad61e9ebe1dbc984157dde0.js
74 ms
plugins-e3c4f55c29a2dab963eb98d2c2420ba6.js
76 ms
app-9b62738536267a929180c93570b406a0.js
52 ms
element.js
199 ms
api.js
102 ms
moment.min-d3e75294221603d2720b916e7bb3c41c.js
71 ms
once_off_tracking-da45b88cb3dbd4cef21b8b156608bcc3.js
72 ms
css
192 ms
main.min.css
27 ms
button.widget.min.js
47 ms
collect
48 ms
collect
84 ms
collect
93 ms
collect
120 ms
icons.data.svg.css
26 ms
hong-kong-post.png
49 ms
translateelement.css
159 ms
main.js
186 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
137 ms
DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf
157 ms
MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf
154 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
185 ms
1eJU4PjErWSV5LNTKFXcze5UHikZLg3viIH581vcHWA.js
12 ms
ad_status.js
80 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
73 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
72 ms
recaptcha__en.js
114 ms
collect
11 ms
element_main.js
52 ms
l
40 ms
cleardot.gif
20 ms
translate_24dp.png
15 ms
aftership.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
button, link, and menuitem elements do not have accessible names.
ARIA IDs are not unique
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
Heading elements are not in a sequentially-descending order
aftership.com 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
Page has valid source maps
aftership.com 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
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Aftership.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 Aftership.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.
aftership.com
Open Graph description is not detected on the main page of After Ship. 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: