Tools & Wizards About Us
optimizely.pagerduty.com screenshot

Report Summary

  • 47

    Performance

    Renders faster than
    66% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 50% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 81

    SEO

    Google-friendlier than
    43% of websites

optimizely.pagerduty.com

PagerDuty

Page Load Speed

1.7 sec in total

First Response

189 ms

Resources Loaded

1.4 sec

Page Rendered

90 ms

optimizely.pagerduty.com screenshot

About Website

Welcome to optimizely.pagerduty.com homepage info - get ready to check Optimizely Pager Duty best content for United States right away, or after learning these important things about optimizely.pagerduty.com

Visit optimizely.pagerduty.com

Key Findings

We analyzed Optimizely.pagerduty.com page load time and found that the first response time was 189 ms and then it took 1.5 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

optimizely.pagerduty.com performance score

47

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

29/100

10%

LCP (Largest Contentful Paint)

Value6.6 s

8/100

25%

SI (Speed Index)

Value4.5 s

72/100

10%

TBT (Total Blocking Time)

Value520 ms

56/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value10.1 s

26/100

10%

Network Requests Diagram

optimizely.pagerduty.com

189 ms

optimizely.pagerduty.com

341 ms

sign_in

128 ms

minimal-ad22a9eca84a061919c5761f6fde97f4.css

52 ms

minimal-d33080b7cec93d6de68093686b464659.js

88 ms

Our browser made a total of 40 requests to load all elements on the main page. We found that 8% of them (3 requests) were addressed to the original Optimizely.pagerduty.com, 15% (6 requests) were made to D15pqkbmbgi02z.cloudfront.net and 8% (3 requests) were made to Pixel.prfct.co. The less responsive or slowest element that took the longest time to load (341 ms) belongs to the original domain Optimizely.pagerduty.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 790.8 kB (81%)

Content Size

980.2 kB

After Optimization

189.4 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Optimizely.pagerduty.com main page is 980.2 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. CSS take 673.9 kB which makes up the majority of the site volume.

HTML Optimization

-65%

Potential reduce by 16.1 kB

  • Original 24.8 kB
  • After minification 24.7 kB
  • After compression 8.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 16.1 kB or 65% of the original size.

JavaScript Optimization

-55%

Potential reduce by 154.8 kB

  • Original 281.6 kB
  • After minification 281.5 kB
  • After compression 126.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 154.8 kB or 55% of the original size.

CSS Optimization

-92%

Potential reduce by 619.9 kB

  • Original 673.9 kB
  • After minification 346.0 kB
  • After compression 54.0 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. Optimizely.pagerduty.com needs all CSS files to be minified and compressed as it can save up to 619.9 kB or 92% of the original size.

Requests Breakdown

Number of requests can be reduced by 29 (88%)

Requests Now

33

After Optimization

4

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

optimizely.pagerduty.com

optimizely.pagerduty.com

189 ms

optimizely.pagerduty.com

optimizely.pagerduty.com

341 ms

sign_in

sign_in

128 ms

minimal-ad22a9eca84a061919c5761f6fde97f4.css

minimal-ad22a9eca84a061919c5761f6fde97f4.css

52 ms

minimal-d33080b7cec93d6de68093686b464659.js

minimal-d33080b7cec93d6de68093686b464659.js

88 ms

bugsnag-2.min.js

bugsnag-2.min.js

45 ms

gtm.js

gtm.js

50 ms

analytics.min.js

analytics.min.js

86 ms

logo-18e1cba552ff56d2ab5945cf43a2279b.svg

logo-18e1cba552ff56d2ab5945cf43a2279b.svg

7 ms

ColfaxWebRegular-808d8a83f5c9127eeb2a9a63e65cf49a.woff

ColfaxWebRegular-808d8a83f5c9127eeb2a9a63e65cf49a.woff

20 ms

ColfaxWebLight-d5c6f65635e4fa7529ef542eabf8614d.otf

ColfaxWebLight-d5c6f65635e4fa7529ef542eabf8614d.otf

26 ms

ColfaxWebMedium-89062e1daf52ec6ad0460ccda620a4a5.woff

ColfaxWebMedium-89062e1daf52ec6ad0460ccda620a4a5.woff

25 ms

conversion_async.js

conversion_async.js

116 ms

537f84849eb8903611000073.js

537f84849eb8903611000073.js

130 ms

oJB4Bebp.min.js

oJB4Bebp.min.js

159 ms

analytics.js

analytics.js

69 ms

cc8865b4fa4bc5bf7761e6718677388e2e3d48aa.2.js

cc8865b4fa4bc5bf7761e6718677388e2e3d48aa.2.js

163 ms

ip.json

ip.json

106 ms

pixel

pixel

89 ms

collect

collect

45 ms

collect

collect

115 ms

collect

collect

56 ms

intercom.21a35ffd.js

intercom.21a35ffd.js

164 ms

76 ms

tagjs

tagjs

4 ms

pixel

pixel

17 ms

94 ms

e

e

87 ms

e

e

95 ms

adsct

adsct

177 ms

Pug

Pug

135 ms

pixel

pixel

132 ms

echo.515e8809.js

echo.515e8809.js

18 ms

cb

cb

24 ms

sd

sd

9 ms

cb

cb

3 ms

tap.php

tap.php

40 ms

ncm

ncm

8 ms

cb

cb

3 ms

nr-885.min.js

nr-885.min.js

42 ms

Accessibility Review

optimizely.pagerduty.com accessibility score

80

Accessibility Issues

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Some elements have a [tabindex] value greater than 0

Best Practices

optimizely.pagerduty.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

Missing source maps for large first-party JavaScript

SEO Factors

optimizely.pagerduty.com SEO score

81

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Page is blocked from indexing

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 Optimizely.pagerduty.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 Optimizely.pagerduty.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

optimizely.pagerduty.com

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