Tools & Wizards About Us
support.incapsula.com screenshot

Report Summary

  • 67

    Performance

    Renders faster than
    80% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

support.incapsula.com

Page Load Speed

1.6 sec in total

First Response

216 ms

Resources Loaded

1.1 sec

Page Rendered

349 ms

support.incapsula.com screenshot

About Website

Visit support.incapsula.com now to see the best up-to-date Support Incapsula content for United States and also check out these interesting facts you probably never knew about support.incapsula.com

Visit support.incapsula.com

Key Findings

We analyzed Support.incapsula.com page load time and found that the first response time was 216 ms and then it took 1.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.

Performance Metrics

support.incapsula.com performance score

67

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

13/100

10%

LCP (Largest Contentful Paint)

Value4.7 s

33/100

25%

SI (Speed Index)

Value5.0 s

64/100

10%

TBT (Total Blocking Time)

Value150 ms

95/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value5.4 s

71/100

10%

Network Requests Diagram

support.incapsula.com

216 ms

hc

148 ms

en-us

210 ms

application-80c7aad11baf60732a806f5ba7f66d94.css

129 ms

style-68a60390a1497d2a9f883a86ee4cfbd9.css

148 ms

Our browser made a total of 33 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Support.incapsula.com, 48% (16 requests) were made to P5.zdassets.com and 33% (11 requests) were made to P2.zdassets.com. The less responsive or slowest element that took the longest time to load (299 ms) relates to the external source P2.zdassets.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 554.3 kB (69%)

Content Size

807.1 kB

After Optimization

252.8 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Support.incapsula.com main page is 807.1 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. 25% of websites need less resources to load. Javascripts take 702.2 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 43.8 kB

  • Original 55.0 kB
  • After minification 41.4 kB
  • After compression 11.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. This page needs HTML code to be minified as it can gain 13.7 kB, which is 25% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 43.8 kB or 80% of the original size.

JavaScript Optimization

-68%

Potential reduce by 474.8 kB

  • Original 702.2 kB
  • After minification 701.3 kB
  • After compression 227.4 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 474.8 kB or 68% of the original size.

CSS Optimization

-72%

Potential reduce by 35.7 kB

  • Original 49.8 kB
  • After minification 49.8 kB
  • After compression 14.2 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. Support.incapsula.com needs all CSS files to be minified and compressed as it can save up to 35.7 kB or 72% of the original size.

Requests Breakdown

Number of requests can be reduced by 6 (21%)

Requests Now

29

After Optimization

23

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

support.incapsula.com

support.incapsula.com

216 ms

hc

hc

148 ms

en-us

en-us

210 ms

application-80c7aad11baf60732a806f5ba7f66d94.css

application-80c7aad11baf60732a806f5ba7f66d94.css

129 ms

style-68a60390a1497d2a9f883a86ee4cfbd9.css

style-68a60390a1497d2a9f883a86ee4cfbd9.css

148 ms

jquery-ded366808f7e9b8657865f599dda349a.js

jquery-ded366808f7e9b8657865f599dda349a.js

178 ms

script-68a60390a1497d2a9f883a86ee4cfbd9.js

script-68a60390a1497d2a9f883a86ee4cfbd9.js

152 ms

locales-dac712b042e8667e923847da41eb3a9080dcaa72.js

locales-dac712b042e8667e923847da41eb3a9080dcaa72.js

152 ms

host.js

host.js

60 ms

vendor_enduser-2ece5393630b699856d9e895b8a3cc1e.js

vendor_enduser-2ece5393630b699856d9e895b8a3cc1e.js

213 ms

hc_enduser-e7e646dd454b715a8f77941eda299930.js

hc_enduser-e7e646dd454b715a8f77941eda299930.js

208 ms

analytics.js

analytics.js

180 ms

1.png

1.png

271 ms

logologo.jpg

logologo.jpg

164 ms

hero_banner.png

hero_banner.png

294 ms

gear.png

gear.png

165 ms

info-kb.png

info-kb.png

166 ms

questionmark.png

questionmark.png

165 ms

points.png

points.png

164 ms

footer-logologo.png

footer-logologo.png

194 ms

2.png

2.png

266 ms

3.png

3.png

268 ms

4.png

4.png

268 ms

5.png

5.png

267 ms

bubble.png

bubble.png

268 ms

phone.png

phone.png

293 ms

fb.png

fb.png

295 ms

tweet.png

tweet.png

297 ms

gplus.png

gplus.png

297 ms

linkdin.png

linkdin.png

299 ms

entypo.svg

entypo.svg

130 ms

entypo.woff

entypo.woff

102 ms

collect

collect

13 ms

Accessibility Review

support.incapsula.com accessibility score

100

Accessibility Issues

Best Practices

support.incapsula.com 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

User Experience

Impact

Issue

High

Serves images with low resolution

SEO Factors

support.incapsula.com 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

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Support.incapsula.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Support.incapsula.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

support.incapsula.com

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