Tools & Wizards About Us
us-postoffice.com screenshot

Report Summary

  • 60

    Performance

    Renders faster than
    76% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 43% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

us-postoffice.com

Postoffice of US | Postal Locations, Services Information and Hours Operation

Page Load Speed

954 ms in total

First Response

63 ms

Resources Loaded

726 ms

Page Rendered

165 ms

us-postoffice.com screenshot

About Website

Click here to check amazing US Postoffice content for United States. Otherwise, check out these important facts you probably never knew about us-postoffice.com

US post offices information. Location, operating hours, phone number, and postal services. Find all post office locations right here and get your mail done today. Find info for a post office in your c...

Visit us-postoffice.com

Key Findings

We analyzed Us-postoffice.com page load time and found that the first response time was 63 ms and then it took 891 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

us-postoffice.com performance score

60

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.7 s

93/100

10%

LCP (Largest Contentful Paint)

Value2.4 s

92/100

25%

SI (Speed Index)

Value5.0 s

63/100

10%

TBT (Total Blocking Time)

Value1,640 ms

12/100

30%

CLS (Cumulative Layout Shift)

Value0.009

100/100

15%

TTI (Time to Interactive)

Value10.3 s

25/100

10%

Network Requests Diagram

us-postoffice.com

63 ms

us-postoffice.com

480 ms

js

87 ms

adsbygoogle.js

115 ms

output.9c56579b8590.css

27 ms

Our browser made a total of 9 requests to load all elements on the main page. We found that 78% of them (7 requests) were addressed to the original Us-postoffice.com, 11% (1 request) were made to Googletagmanager.com and 11% (1 request) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (480 ms) belongs to the original domain Us-postoffice.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 47.8 kB (34%)

Content Size

139.0 kB

After Optimization

91.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-77%

Potential reduce by 11.6 kB

  • Original 15.2 kB
  • After minification 11.3 kB
  • After compression 3.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. This page needs HTML code to be minified as it can gain 3.9 kB, which is 26% 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 11.6 kB or 77% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 18.9 kB
  • After minification 18.9 kB

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. US Postoffice images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 26 B

  • Original 62.2 kB
  • After minification 62.2 kB
  • After compression 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. This website has mostly compressed JavaScripts.

CSS Optimization

-85%

Potential reduce by 36.2 kB

  • Original 42.8 kB
  • After minification 29.2 kB
  • After compression 6.6 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. Us-postoffice.com needs all CSS files to be minified and compressed as it can save up to 36.2 kB or 85% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

6

After Optimization

6

  • Images
  • JavaScript
  • CSS

The browser has sent 6 CSS, Javascripts, AJAX and image requests in order to completely render the main page of US Postoffice. According to our analytics all requests are already optimized.

Network Requests Diagram

us-postoffice.com

us-postoffice.com

63 ms

us-postoffice.com

us-postoffice.com

480 ms

js

js

87 ms

adsbygoogle.js

adsbygoogle.js

115 ms

output.9c56579b8590.css

output.9c56579b8590.css

27 ms

output.742067a1d015.js

output.742067a1d015.js

51 ms

logo.svg

logo.svg

82 ms

map-1.jpg

map-1.jpg

85 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

31 ms

Accessibility Review

us-postoffice.com accessibility score

76

Accessibility Issues

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

High

[aria-*] attributes do not match their roles

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

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

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

us-postoffice.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

us-postoffice.com SEO score

100

Search Engine Optimization Advices

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    VI

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Us-postoffice.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Vietnamese language. Our system also found out that Us-postoffice.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.

Social Sharing Optimization

us-postoffice.com

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