Tools & Wizards About Us
intheloop.io screenshot

Report Summary

  • 24

    Performance

    Renders faster than
    43% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 66% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 88

    SEO

    Google-friendlier than
    65% of websites

intheloop.io

Loop Email - All-in-one Shared Inbox and Team Email Platform

Page Load Speed

2 sec in total

First Response

144 ms

Resources Loaded

1.3 sec

Page Rendered

597 ms

intheloop.io screenshot

About Website

Welcome to intheloop.io homepage info - get ready to check Inthe Loop best content for United States right away, or after learning these important things about intheloop.io

Loop Email unlocks teamwork right inside your email inbox. It's an all-in-one shared inbox that transforms email into your team’s superpower.

Visit intheloop.io

Key Findings

We analyzed Intheloop.io page load time and found that the first response time was 144 ms and then it took 1.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

intheloop.io performance score

24

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.8 s

4/100

10%

LCP (Largest Contentful Paint)

Value13.9 s

0/100

25%

SI (Speed Index)

Value6.9 s

33/100

10%

TBT (Total Blocking Time)

Value1,520 ms

13/100

30%

CLS (Cumulative Layout Shift)

Value0.019

100/100

15%

TTI (Time to Interactive)

Value14.2 s

9/100

10%

Network Requests Diagram

intheloop.io

144 ms

www.intheloop.io

369 ms

embed.min.js

78 ms

classic-themes.min.css

56 ms

cbxchangelog-public.css

57 ms

Our browser made a total of 81 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Intheloop.io, 75% (61 requests) were made to Cdn.intheloop.io and 12% (10 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (369 ms) belongs to the original domain Intheloop.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 174.1 kB (13%)

Content Size

1.3 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Intheloop.io main page is 1.3 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. Only a small number of websites need less resources to load. Images take 682.5 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 169.6 kB

  • Original 203.8 kB
  • After minification 199.1 kB
  • After compression 34.2 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 169.6 kB or 83% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 682.5 kB
  • After minification 682.5 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. Inthe Loop images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 725 B

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

CSS Optimization

-9%

Potential reduce by 3.9 kB

  • Original 43.2 kB
  • After minification 43.2 kB
  • After compression 39.4 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. Intheloop.io has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 34 (51%)

Requests Now

67

After Optimization

33

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

intheloop.io

intheloop.io

144 ms

www.intheloop.io

www.intheloop.io

369 ms

embed.min.js

embed.min.js

78 ms

classic-themes.min.css

classic-themes.min.css

56 ms

cbxchangelog-public.css

cbxchangelog-public.css

57 ms

styles.css

styles.css

57 ms

css

css

61 ms

cf7-material-design.css

cf7-material-design.css

59 ms

rs6.css

rs6.css

59 ms

style.min.css

style.min.css

58 ms

jquery.min.js

jquery.min.js

58 ms

jquery-migrate.min.js

jquery-migrate.min.js

58 ms

rbtools.min.js

rbtools.min.js

69 ms

rs6.min.js

rs6.min.js

63 ms

98f9b0c10c.js

98f9b0c10c.js

271 ms

et-core-unified-240214.min.css

et-core-unified-240214.min.css

59 ms

css

css

66 ms

index.js

index.js

57 ms

index.js

index.js

57 ms

autosize.min.js

autosize.min.js

57 ms

cf7-material-design-bundle.js

cf7-material-design-bundle.js

64 ms

scripts.min.js

scripts.min.js

62 ms

jquery.fitvids.js

jquery.fitvids.js

60 ms

jquery.mobile.js

jquery.mobile.js

61 ms

frontend-bundle.min.js

frontend-bundle.min.js

64 ms

new-tab.js

new-tab.js

64 ms

common.js

common.js

68 ms

lazyload.min.js

lazyload.min.js

66 ms

gtm.js

gtm.js

94 ms

diffuser.js

diffuser.js

132 ms

mixpanel-2-latest.min.js

mixpanel-2-latest.min.js

133 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVQ.woff

107 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf

255 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVQ.woff

256 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf

274 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVQ.woff

273 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf

274 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVQ.woff

273 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf

271 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVQ.woff

271 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVc.ttf

282 ms

Group-23618.svg

Group-23618.svg

40 ms

modules.ttf

modules.ttf

93 ms

Rectangle-90.svg

Rectangle-90.svg

93 ms

CircularStd-Bold.ttf

CircularStd-Bold.ttf

58 ms

logo.svg

logo.svg

102 ms

prism.app-us1.com

prism.app-us1.com

232 ms

Rectangle-71.svg

Rectangle-71.svg

44 ms

Rectangle-65.png

Rectangle-65.png

42 ms

Group-23603-2.svg

Group-23603-2.svg

44 ms

Group-23604-1.svg

Group-23604-1.svg

41 ms

Group-23582-5.svg

Group-23582-5.svg

45 ms

Group-23579-7.png

Group-23579-7.png

54 ms

transparent.png

transparent.png

54 ms

1-screen.png

1-screen.png

54 ms

2-screen.png

2-screen.png

53 ms

3-screen.png

3-screen.png

53 ms

4-screen.png

4-screen.png

52 ms

5-screen.png

5-screen.png

55 ms

6-screen.png

6-screen.png

55 ms

7-screen.png

7-screen.png

55 ms

8-screen.png

8-screen.png

73 ms

9-screen.png

9-screen.png

56 ms

10-screen.png

10-screen.png

54 ms

11-screen.png

11-screen.png

75 ms

12-screen.png

12-screen.png

74 ms

13-screen.png

13-screen.png

75 ms

14-screen.png

14-screen.png

75 ms

15-screen.png

15-screen.png

73 ms

6-homepage-1.gif

6-homepage-1.gif

76 ms

1-homepage-1.gif

1-homepage-1.gif

86 ms

2-homepage-1.gif

2-homepage-1.gif

81 ms

3-homepage.gif

3-homepage.gif

78 ms

4-homepage-1.gif

4-homepage-1.gif

80 ms

5-homepage-1.gif

5-homepage-1.gif

79 ms

2.svg

2.svg

75 ms

1.svg

1.svg

77 ms

Group-23585-8.svg

Group-23585-8.svg

81 ms

bostjan_demoCall.png

bostjan_demoCall.png

82 ms

logo-footer.svg

logo-footer.svg

82 ms

Group-14.png

Group-14.png

85 ms

Accessibility Review

intheloop.io accessibility score

87

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Links do not have a discernible name

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

intheloop.io best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

intheloop.io SEO score

88

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

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 Intheloop.io 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 Intheloop.io 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

intheloop.io

Open Graph data is detected on the main page of Inthe Loop. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: