Tools & Wizards About Us
docs.logentries.com screenshot

Report Summary

  • 24

    Performance

    Renders faster than
    43% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 49% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 71

    SEO

    Google-friendlier than
    30% of websites

docs.logentries.com

InsightIDR Overview | InsightIDR Documentation

Page Load Speed

2.1 sec in total

First Response

7 ms

Resources Loaded

1.3 sec

Page Rendered

806 ms

docs.logentries.com screenshot

About Website

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

Visit docs.logentries.com

Key Findings

We analyzed Docs.logentries.com page load time and found that the first response time was 7 ms and then it took 2.1 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

docs.logentries.com performance score

24

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

44/100

10%

LCP (Largest Contentful Paint)

Value7.9 s

3/100

25%

SI (Speed Index)

Value8.5 s

17/100

10%

TBT (Total Blocking Time)

Value1,950 ms

8/100

30%

CLS (Cumulative Layout Shift)

Value0.014

100/100

15%

TTI (Time to Interactive)

Value20.6 s

2/100

10%

Network Requests Diagram

docs.logentries.com

7 ms

docs.logentries.com

15 ms

310 ms

css2

34 ms

app.css

454 ms

Our browser made a total of 31 requests to load all elements on the main page. We found that 6% of them (2 requests) were addressed to the original Docs.logentries.com, 55% (17 requests) were made to Docs.rapid7.com and 16% (5 requests) were made to Rapid7.com. The less responsive or slowest element that took the longest time to load (921 ms) relates to the external source Docs.rapid7.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.0 MB (38%)

Content Size

5.2 MB

After Optimization

3.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Docs.logentries.com main page is 5.2 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. 40% of websites need less resources to load. Images take 4.6 MB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 310.4 kB

  • Original 350.7 kB
  • After minification 348.7 kB
  • After compression 40.3 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 310.4 kB or 89% of the original size.

Image Optimization

-37%

Potential reduce by 1.7 MB

  • Original 4.6 MB
  • After minification 2.9 MB

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. Obviously, Docs Logentries needs image optimization as it can save up to 1.7 MB or 37% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 77 B

  • Original 200.3 kB
  • After minification 200.3 kB
  • After compression 200.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

-0%

Potential reduce by 0 B

  • Original 67.5 kB
  • After minification 67.5 kB
  • After compression 67.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. Docs.logentries.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 10 (43%)

Requests Now

23

After Optimization

13

  • Images
  • JavaScript
  • CSS

The browser has sent 23 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Docs Logentries. 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

docs.logentries.com

docs.logentries.com

7 ms

docs.logentries.com

docs.logentries.com

15 ms

310 ms

css2

css2

34 ms

app.css

app.css

454 ms

css2

css2

53 ms

runtime.bundle.js

runtime.bundle.js

202 ms

vendor.bundle.js

vendor.bundle.js

380 ms

app.bundle.js

app.bundle.js

600 ms

gtm.js

gtm.js

67 ms

Rapid7_logo.svg

Rapid7_logo.svg

198 ms

icon-lock.svg

icon-lock.svg

265 ms

Rapid7_logo-short.svg

Rapid7_logo-short.svg

344 ms

idr-detection-response-diagram.png

idr-detection-response-diagram.png

830 ms

insightidr-architecture.png

insightidr-architecture.png

921 ms

Advanced_CloudSIEM_XDR_graphic.png

Advanced_CloudSIEM_XDR_graphic.png

605 ms

icon-thumbs-up.svg

icon-thumbs-up.svg

552 ms

rapid7-officialpartner-darkbg.png

rapid7-officialpartner-darkbg.png

539 ms

response.svg

response.svg

148 ms

arrow-dropdown.svg

arrow-dropdown.svg

109 ms

dotted-line.svg

dotted-line.svg

362 ms

icon-link.svg

icon-link.svg

369 ms

linkedin-light.svg

linkedin-light.svg

122 ms

twitter-light.svg

twitter-light.svg

148 ms

facebook-light.svg

facebook-light.svg

147 ms

instagram-light.svg

instagram-light.svg

146 ms

KFOmCnqEu92Fr1Me5Q.ttf

KFOmCnqEu92Fr1Me5Q.ttf

65 ms

KFOlCnqEu92Fr1MmWUlvAw.ttf

KFOlCnqEu92Fr1MmWUlvAw.ttf

102 ms

rapid7-icon-font.woff

rapid7-icon-font.woff

407 ms

1Ptyg83HX_SGhgqO0yLcmjzUAuWexRNWwaA.ttf

1Ptyg83HX_SGhgqO0yLcmjzUAuWexRNWwaA.ttf

114 ms

1Ptyg83HX_SGhgqO0yLcmjzUAuWexTpWwaA.ttf

1Ptyg83HX_SGhgqO0yLcmjzUAuWexTpWwaA.ttf

113 ms

Accessibility Review

docs.logentries.com accessibility score

80

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

button, link, and menuitem elements do not have accessible names.

High

ARIA IDs are not unique

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

High

Links do not have a discernible name

Best Practices

docs.logentries.com best practices score

92

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

SEO Factors

docs.logentries.com SEO score

71

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

High

Image elements do not have [alt] attributes

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

docs.logentries.com

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