Tools & Wizards About Us
insurepost.com screenshot

Report Summary

  • 71

    Performance

    Renders faster than
    81% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

insurepost.com

Shipping Insurance has Moved to ShipSaver.com

Page Load Speed

1.5 sec in total

First Response

34 ms

Resources Loaded

1.4 sec

Page Rendered

97 ms

insurepost.com screenshot

About Website

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

InsurePost Shipping Insurance has Moved to ShipSaver.com - Purchase Instant Shipping Insurance Coveraage for Your Packages. If you ship via FedEx, UPS, the USPS (United States Postal Service), or DHL ...

Visit insurepost.com

Key Findings

We analyzed Insurepost.com page load time and found that the first response time was 34 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.

Performance Metrics

insurepost.com performance score

71

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

47/100

10%

LCP (Largest Contentful Paint)

Value4.1 s

46/100

25%

SI (Speed Index)

Value3.1 s

93/100

10%

TBT (Total Blocking Time)

Value320 ms

77/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value5.4 s

71/100

10%

Network Requests Diagram

insurepost.com

34 ms

insurepost.com

186 ms

www.insurepost.com

197 ms

shipsaver.asp

55 ms

gtm.js

64 ms

Our browser made a total of 19 requests to load all elements on the main page. We found that 58% of them (11 requests) were addressed to the original Insurepost.com, 21% (4 requests) were made to Apis.google.com and 11% (2 requests) were made to Ssl.google-analytics.com. The less responsive or slowest element that took the longest time to load (510 ms) relates to the external source Developers.google.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 9.9 kB (6%)

Content Size

162.1 kB

After Optimization

152.2 kB

  • HTML
  • JavaScript
  • CSS

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

HTML Optimization

-69%

Potential reduce by 8.9 kB

  • Original 13.0 kB
  • After minification 12.0 kB
  • After compression 4.1 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 8.9 kB or 69% of the original size.

JavaScript Optimization

-0%

Potential reduce by 169 B

  • Original 146.6 kB
  • After minification 146.6 kB
  • After compression 146.4 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.

CSS Optimization

-31%

Potential reduce by 771 B

  • Original 2.5 kB
  • After minification 2.5 kB
  • After compression 1.7 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. Insurepost.com needs all CSS files to be minified and compressed as it can save up to 771 B or 31% of the original size.

Requests Breakdown

Number of requests can be reduced by 5 (36%)

Requests Now

14

After Optimization

9

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

insurepost.com

insurepost.com

34 ms

insurepost.com

insurepost.com

186 ms

www.insurepost.com

www.insurepost.com

197 ms

shipsaver.asp

shipsaver.asp

55 ms

gtm.js

gtm.js

64 ms

style.css

style.css

146 ms

plusone.js

plusone.js

26 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

25 ms

ga.js

ga.js

31 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

20 ms

insurepost_logo_1.gif

insurepost_logo_1.gif

152 ms

member_back.gif

member_back.gif

207 ms

members.gif

members.gif

189 ms

cb=gapi.loaded_2

cb=gapi.loaded_2

38 ms

__utm.gif

__utm.gif

12 ms

developers.google.com

developers.google.com

510 ms

front_main_red_r2_c2_f2.gif

front_main_red_r2_c2_f2.gif

176 ms

front_main_red_r2_c3_f3.gif

front_main_red_r2_c3_f3.gif

95 ms

front_logos_03_on.gif

front_logos_03_on.gif

177 ms

Accessibility Review

insurepost.com accessibility score

81

Accessibility Issues

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

<frame> or <iframe> elements do not have a title

High

Form elements do not have associated labels

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

insurepost.com best practices score

58

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

insurepost.com SEO score

69

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Insurepost.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Insurepost.com main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

insurepost.com

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