Tools & Wizards About Us
puresec.io screenshot

Report Summary

  • 69

    Performance

    Renders faster than
    80% of other websites

  • 99

    Accessibility

    Visual factors better than
    that of 96% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

puresec.io

Cloud Workload Protection (CWP) | CWPP - Palo Alto Networks

Page Load Speed

3 sec in total

First Response

118 ms

Resources Loaded

883 ms

Page Rendered

2 sec

puresec.io screenshot

About Website

Click here to check amazing Puresec content for United States. Otherwise, check out these important facts you probably never knew about puresec.io

Cloud workload protection ensures workloads that move across cloud environments are secure. Explore Palo Alto Networks’ CWP solution offerings.

Visit puresec.io

Key Findings

We analyzed Puresec.io page load time and found that the first response time was 118 ms and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

puresec.io performance score

69

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.6 s

62/100

10%

LCP (Largest Contentful Paint)

Value6.0 s

13/100

25%

SI (Speed Index)

Value4.3 s

76/100

10%

TBT (Total Blocking Time)

Value40 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value5.3 s

73/100

10%

Network Requests Diagram

puresec.io

118 ms

cloud-workload-protection-platform

183 ms

lazyload.min.js

13 ms

promise-polyfill-8.2.1.js

13 ms

polyfill-object-fit-images-3.2.4.js

21 ms

Our browser made a total of 32 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Puresec.io, 88% (28 requests) were made to Paloaltonetworks.com and 3% (1 request) were made to Assets.adobedtm.com. The less responsive or slowest element that took the longest time to load (573 ms) relates to the external source Paloaltonetworks.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.2 MB (42%)

Content Size

2.8 MB

After Optimization

1.6 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Puresec.io main page is 2.8 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. 60% of websites need less resources to load. Images take 1.7 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 767.0 kB

  • Original 933.7 kB
  • After minification 926.7 kB
  • After compression 166.8 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 767.0 kB or 82% of the original size.

Image Optimization

-25%

Potential reduce by 429.3 kB

  • Original 1.7 MB
  • After minification 1.3 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, Puresec needs image optimization as it can save up to 429.3 kB or 25% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-1%

Potential reduce by 1.9 kB

  • Original 160.7 kB
  • After minification 160.7 kB
  • After compression 158.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.

Requests Breakdown

Number of requests can be reduced by 18 (60%)

Requests Now

30

After Optimization

12

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

puresec.io

puresec.io

118 ms

cloud-workload-protection-platform

cloud-workload-protection-platform

183 ms

lazyload.min.js

lazyload.min.js

13 ms

promise-polyfill-8.2.1.js

promise-polyfill-8.2.1.js

13 ms

polyfill-object-fit-images-3.2.4.js

polyfill-object-fit-images-3.2.4.js

21 ms

launch-425c423d843b.min.js

launch-425c423d843b.min.js

93 ms

6KU9W-5DTLL-AXSJY-VNWUZ-RTS7Q

6KU9W-5DTLL-AXSJY-VNWUZ-RTS7Q

42 ms

bundle.dprisma.poperbscolbsdroddeanddebaddefeddelhddeltddepgddespddetiddetxddybadmftcdprcbdprdgdprhedprptdprsidprtedprtfdsutcdprmn.min.11aab4914977a5471faf0b2185014c2a.js

bundle.dprisma.poperbscolbsdroddeanddebaddefeddelhddeltddepgddespddetiddetxddybadmftcdprcbdprdgdprhedprptdprsidprtedprtfdsutcdprmn.min.11aab4914977a5471faf0b2185014c2a.js

260 ms

bundle.dprisma.poperbscolbsdroddeanddebaddefeddelhddeltddepgddespddetiddetxddybadmftcdprcbdprdgdprhedprptdprsidprtedprtfdsutcdprmn.min.11aab4914977a5471faf0b2185014c2a.css

bundle.dprisma.poperbscolbsdroddeanddebaddefeddelhddeltddepgddespddetiddetxddybadmftcdprcbdprdgdprhedprptdprsidprtedprtfdsutcdprmn.min.11aab4914977a5471faf0b2185014c2a.css

301 ms

prisma-logo-light.svg

prisma-logo-light.svg

443 ms

search-white.svg

search-white.svg

48 ms

logo-default.svg

logo-default.svg

32 ms

arrow-right-white.svg

arrow-right-white.svg

31 ms

prisma-hero-banner-new.jpg

prisma-hero-banner-new.jpg

293 ms

arrow-right-black.svg

arrow-right-black.svg

42 ms

cwpp-hero-front.png

cwpp-hero-front.png

62 ms

cwpp-hero-back.png

cwpp-hero-back.png

366 ms

prisma-cloud_container-security-ondemand-webinar_pc-homepage-banner_1920x1080.jpg

prisma-cloud_container-security-ondemand-webinar_pc-homepage-banner_1920x1080.jpg

573 ms

chevron-left-white.svg

chevron-left-white.svg

295 ms

chevron-right-white.svg

chevron-right-white.svg

293 ms

prisma-triangle-pattern-bg.png

prisma-triangle-pattern-bg.png

336 ms

check-blue.svg

check-blue.svg

295 ms

solution-light-bg.png

solution-light-bg.png

297 ms

logo-prisma.svg

logo-prisma.svg

499 ms

prisma-beams-card-bg.svg

prisma-beams-card-bg.svg

337 ms

icon-prisma-white.svg

icon-prisma-white.svg

448 ms

chevron-left-black.svg

chevron-left-black.svg

345 ms

chevron-right-black.svg

chevron-right-black.svg

353 ms

chevron-down-black.svg

chevron-down-black.svg

358 ms

userHeaderModel

userHeaderModel

444 ms

config.json

config.json

65 ms

singlePageReactModel

singlePageReactModel

132 ms

Accessibility Review

puresec.io accessibility score

99

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

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

High

Page has valid source maps

SEO Factors

puresec.io SEO score

93

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

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 Puresec.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 Puresec.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

puresec.io

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