Tools & Wizards About Us
gmail.inbox.com screenshot

Report Summary

  • 57

    Performance

    Renders faster than
    73% of other websites

  • 59

    Accessibility

    Visual factors better than
    that of 26% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

gmail.inbox.com

Reliable Email Provider, Inbox Email & Resource Center | inbox.com

Page Load Speed

1.2 sec in total

First Response

291 ms

Resources Loaded

694 ms

Page Rendered

194 ms

gmail.inbox.com screenshot

About Website

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

Simplify your online communication with one login to secure email communication, organize conversations, and fine-tune archive searches.

Visit gmail.inbox.com

Key Findings

We analyzed Gmail.inbox.com page load time and found that the first response time was 291 ms and then it took 888 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.

Performance Metrics

gmail.inbox.com performance score

57

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.8 s

90/100

10%

LCP (Largest Contentful Paint)

Value3.6 s

61/100

25%

SI (Speed Index)

Value1.8 s

100/100

10%

TBT (Total Blocking Time)

Value1,980 ms

8/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value7.0 s

53/100

10%

Network Requests Diagram

gmail.inbox.com

291 ms

hp.css

116 ms

hp.css

113 ms

preusr.js

115 ms

usr.js

112 ms

Our browser made a total of 30 requests to load all elements on the main page. We found that 13% of them (4 requests) were addressed to the original Gmail.inbox.com, 57% (17 requests) were made to Inbox.com and 10% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (291 ms) belongs to the original domain Gmail.inbox.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 102.0 kB (48%)

Content Size

212.4 kB

After Optimization

110.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-74%

Potential reduce by 44.8 kB

  • Original 60.5 kB
  • After minification 60.5 kB
  • After compression 15.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 44.8 kB or 74% of the original size.

Image Optimization

-2%

Potential reduce by 906 B

  • Original 56.7 kB
  • After minification 55.8 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. Gmail Inbox images are well optimized though.

JavaScript Optimization

-50%

Potential reduce by 30.7 kB

  • Original 61.9 kB
  • After minification 61.7 kB
  • After compression 31.1 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 30.7 kB or 50% of the original size.

CSS Optimization

-77%

Potential reduce by 25.6 kB

  • Original 33.3 kB
  • After minification 31.0 kB
  • After compression 7.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. Gmail.inbox.com needs all CSS files to be minified and compressed as it can save up to 25.6 kB or 77% of the original size.

Requests Breakdown

Number of requests can be reduced by 13 (48%)

Requests Now

27

After Optimization

14

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

gmail.inbox.com

gmail.inbox.com

291 ms

hp.css

hp.css

116 ms

hp.css

hp.css

113 ms

preusr.js

preusr.js

115 ms

usr.js

usr.js

112 ms

image-1385729-10517611

image-1385729-10517611

12 ms

image-1385729-10482812

image-1385729-10482812

13 ms

ar.aspx

ar.aspx

71 ms

showers.gif

showers.gif

35 ms

logo.gif

logo.gif

34 ms

st-dart.gif

st-dart.gif

35 ms

tt.gif

tt.gif

34 ms

box-crn.gif

box-crn.gif

62 ms

cubes.gif

cubes.gif

65 ms

comic1865.jpg

comic1865.jpg

99 ms

sbox-img.gif

sbox-img.gif

99 ms

sbox-bg.gif

sbox-bg.gif

65 ms

ssl-lock.gif

ssl-lock.gif

65 ms

sbox-get.gif

sbox-get.gif

66 ms

sbox-h4n.gif

sbox-h4n.gif

98 ms

tstorm.gif

tstorm.gif

61 ms

ga.js

ga.js

6 ms

user.gif

user.gif

68 ms

GetXML5

GetXML5

40 ms

__utm.gif

__utm.gif

12 ms

__utm.gif

__utm.gif

11 ms

flash.js

flash.js

36 ms

collect

collect

63 ms

abox-bg-inbox.gif

abox-bg-inbox.gif

30 ms

PrimeSender_3612a_424x165.jpg

PrimeSender_3612a_424x165.jpg

196 ms

Accessibility Review

gmail.inbox.com accessibility score

59

Accessibility Issues

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

Image elements do not have [alt] attributes

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

gmail.inbox.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

SEO Factors

gmail.inbox.com SEO score

82

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Content Best Practices

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

Impact

Issue

High

Image elements do not have [alt] attributes

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Gmail.inbox.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 Gmail.inbox.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

gmail.inbox.com

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