Tools & Wizards About Us
inbox.im screenshot

Report Summary

  • 51

    Performance

    Renders faster than
    69% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

inbox.im

INBOX.IM

Page Load Speed

2 sec in total

First Response

379 ms

Resources Loaded

1.5 sec

Page Rendered

187 ms

inbox.im screenshot

About Website

Click here to check amazing INBOX content for Cuba. Otherwise, check out these important facts you probably never knew about inbox.im

Visit inbox.im

Key Findings

We analyzed Inbox.im page load time and found that the first response time was 379 ms and then it took 1.6 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

inbox.im performance score

51

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

53/100

10%

LCP (Largest Contentful Paint)

Value3.2 s

71/100

25%

SI (Speed Index)

Value5.2 s

60/100

10%

TBT (Total Blocking Time)

Value1,160 ms

22/100

30%

CLS (Cumulative Layout Shift)

Value0.089

92/100

15%

TTI (Time to Interactive)

Value11.6 s

18/100

10%

Network Requests Diagram

inbox.im

379 ms

bootstrap.min.css

231 ms

custom.css

243 ms

bootstrap-responsive.min.css

241 ms

modernizr-2.6.2.min.js

360 ms

Our browser made a total of 39 requests to load all elements on the main page. We found that 41% of them (16 requests) were addressed to the original Inbox.im, 13% (5 requests) were made to Pagead2.googlesyndication.com and 13% (5 requests) were made to Googleads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (379 ms) belongs to the original domain Inbox.im.

Page Optimization Overview & Recommendations

Page size can be reduced by 117.8 kB (50%)

Content Size

235.8 kB

After Optimization

117.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Inbox.im main page is 235.8 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. 45% of websites need less resources to load. CSS take 119.9 kB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 6.5 kB

  • Original 9.2 kB
  • After minification 9.1 kB
  • After compression 2.6 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 6.5 kB or 71% of the original size.

Image Optimization

-7%

Potential reduce by 4.7 kB

  • Original 62.9 kB
  • After minification 58.2 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. INBOX images are well optimized though.

JavaScript Optimization

-16%

Potential reduce by 7.2 kB

  • Original 43.8 kB
  • After minification 43.6 kB
  • After compression 36.6 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 7.2 kB or 16% of the original size.

CSS Optimization

-83%

Potential reduce by 99.4 kB

  • Original 119.9 kB
  • After minification 119.9 kB
  • After compression 20.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. Inbox.im needs all CSS files to be minified and compressed as it can save up to 99.4 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 20 (54%)

Requests Now

37

After Optimization

17

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 37 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 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 13 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

inbox.im

inbox.im

379 ms

bootstrap.min.css

bootstrap.min.css

231 ms

custom.css

custom.css

243 ms

bootstrap-responsive.min.css

bootstrap-responsive.min.css

241 ms

modernizr-2.6.2.min.js

modernizr-2.6.2.min.js

360 ms

show_ads.js

show_ads.js

8 ms

gibberish-aes.min.js

gibberish-aes.min.js

247 ms

jquery.min.js

jquery.min.js

30 ms

bootstrap.min.js

bootstrap.min.js

246 ms

linen.jpg

linen.jpg

232 ms

logo-white.png

logo-white.png

232 ms

glyphicons-halflings.png

glyphicons-halflings.png

236 ms

message.png

message.png

232 ms

my_topic.png

my_topic.png

228 ms

xmpp.png

xmpp.png

229 ms

wow.png

wow.png

231 ms

globe.png

globe.png

233 ms

cuba.png

cuba.png

233 ms

ca-pub-9450785255587031.js

ca-pub-9450785255587031.js

69 ms

zrt_lookup.html

zrt_lookup.html

166 ms

show_ads_impl.js

show_ads_impl.js

53 ms

ga.js

ga.js

79 ms

logger.io.js

logger.io.js

194 ms

ads

ads

218 ms

osd.js

osd.js

49 ms

ads

ads

190 ms

__utm.gif

__utm.gif

42 ms

ads

ads

208 ms

css

css

69 ms

m_js_controller.js

m_js_controller.js

40 ms

abg.js

abg.js

43 ms

favicon

favicon

106 ms

nessie_icon_tiamat_white.png

nessie_icon_tiamat_white.png

72 ms

s

s

66 ms

googlelogo_color_112x36dp.png

googlelogo_color_112x36dp.png

163 ms

favicon

favicon

73 ms

x_button_blue2.svg

x_button_blue2.svg

33 ms

fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js

fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js

25 ms

Hgo13k-tfSpn0qi1SFdUfSZ2oysoEQEeKwjgmXLRnTc.ttf

Hgo13k-tfSpn0qi1SFdUfSZ2oysoEQEeKwjgmXLRnTc.ttf

112 ms

Accessibility Review

inbox.im accessibility score

83

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

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

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

inbox.im best practices score

67

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

inbox.im SEO score

85

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

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

    ES

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Inbox.im can be misinterpreted by Google and other search engines. Our service has detected that Spanish 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 Inbox.im 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

inbox.im

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