Tools & Wizards About Us
complianz.io screenshot

Report Summary

  • 76

    Performance

    Renders faster than
    84% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 74% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 97

    SEO

    Google-friendlier than
    91% of websites

complianz.io

The Privacy Suite for WordPress - GDPR/CCPA/PECR and more.

Page Load Speed

3.1 sec in total

First Response

55 ms

Resources Loaded

2.8 sec

Page Rendered

317 ms

complianz.io screenshot

About Website

Visit complianz.io now to see the best up-to-date Complianz content for India and also check out these interesting facts you probably never knew about complianz.io

The only Privacy Suite for WordPress - Get ready for GDPR, ePrivacy, CCPA and more. Brought to you by Really Simple SSL and the Complianz Team.

Visit complianz.io

Key Findings

We analyzed Complianz.io page load time and found that the first response time was 55 ms and then it took 3.1 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

complianz.io performance score

76

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

75/100

10%

LCP (Largest Contentful Paint)

Value5.2 s

23/100

25%

SI (Speed Index)

Value2.3 s

99/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.004

100/100

15%

TTI (Time to Interactive)

Value4.5 s

82/100

10%

Network Requests Diagram

complianz.io

55 ms

complianz.io

296 ms

edd-blocks.css

208 ms

edd-mb.min.css

201 ms

forms.min.css

199 ms

Our browser made a total of 75 requests to load all elements on the main page. We found that all of those requests were addressed to Complianz.io and no external sources were called. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Complianz.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 119.2 kB (64%)

Content Size

187.2 kB

After Optimization

68.0 kB

  • HTML
  • Images

In fact, the total size of Complianz.io main page is 187.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. 35% of websites need less resources to load. HTML takes 131.5 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 111.5 kB

  • Original 131.5 kB
  • After minification 124.4 kB
  • After compression 20.0 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 111.5 kB or 85% of the original size.

Image Optimization

-14%

Potential reduce by 7.8 kB

  • Original 55.7 kB
  • After minification 47.9 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. Obviously, Complianz needs image optimization as it can save up to 7.8 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

Requests Breakdown

Number of requests can be reduced by 57 (93%)

Requests Now

61

After Optimization

4

  • Images
  • JavaScript
  • CSS

The browser has sent 61 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Complianz. 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 38 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

complianz.io

complianz.io

55 ms

complianz.io

complianz.io

296 ms

edd-blocks.css

edd-blocks.css

208 ms

edd-mb.min.css

edd-mb.min.css

201 ms

forms.min.css

forms.min.css

199 ms

edd.min.css

edd.min.css

206 ms

cookieblocker.min.css

cookieblocker.min.css

197 ms

styles.css

styles.css

260 ms

style-frontend.css

style-frontend.css

378 ms

styles.css

styles.css

379 ms

style.min.css

style.min.css

383 ms

theme.min.css

theme.min.css

422 ms

header-footer.min.css

header-footer.min.css

391 ms

elementor-icons.min.css

elementor-icons.min.css

440 ms

custom-frontend.min.css

custom-frontend.min.css

561 ms

swiper.min.css

swiper.min.css

560 ms

e-swiper.min.css

e-swiper.min.css

565 ms

post-26078.css

post-26078.css

583 ms

custom-pro-frontend.min.css

custom-pro-frontend.min.css

608 ms

all.min.css

all.min.css

620 ms

v4-shims.min.css

v4-shims.min.css

740 ms

global.css

global.css

742 ms

widget-heading.min.css

widget-heading.min.css

749 ms

widget-text-editor.min.css

widget-text-editor.min.css

767 ms

custom-widget-icon-list.min.css

custom-widget-icon-list.min.css

788 ms

custom-widget-star-rating.min.css

custom-widget-star-rating.min.css

631 ms

widget-image.min.css

widget-image.min.css

882 ms

post-601.css

post-601.css

749 ms

post-197270.css

post-197270.css

927 ms

post-197271.css

post-197271.css

936 ms

post-521726.css

post-521726.css

928 ms

google-fonts-1.css

google-fonts-1.css

863 ms

fontawesome.min.css

fontawesome.min.css

971 ms

brands.min.css

brands.min.css

1044 ms

solid.min.css

solid.min.css

1063 ms

jquery.min.js

jquery.min.js

1108 ms

jquery-migrate.min.js

jquery-migrate.min.js

1118 ms

widget-social-icons.min.css

widget-social-icons.min.css

1050 ms

apple-webkit.min.css

apple-webkit.min.css

965 ms

widget-spacer.min.css

widget-spacer.min.css

1030 ms

fadeInUp.min.css

fadeInUp.min.css

1054 ms

v4-shims.min.js

v4-shims.min.js

1087 ms

run_prettify.js

run_prettify.js

1126 ms

api-request.min.js

api-request.min.js

1073 ms

edd-mb.min.js

edd-mb.min.js

1062 ms

edd-ajax.js

edd-ajax.js

1062 ms

imagesloaded.min.js

imagesloaded.min.js

1059 ms

complianz.min.js

complianz.min.js

1093 ms

jquery.smartmenus.min.js

jquery.smartmenus.min.js

1061 ms

jquery.sticky.min.js

jquery.sticky.min.js

1053 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

962 ms

webpack.runtime.min.js

webpack.runtime.min.js

1030 ms

frontend-modules.min.js

frontend-modules.min.js

1059 ms

hooks.min.js

hooks.min.js

992 ms

i18n.min.js

i18n.min.js

1047 ms

frontend.min.js

frontend.min.js

1069 ms

core.min.js

core.min.js

1071 ms

frontend.min.js

frontend.min.js

1018 ms

elements-handlers.min.js

elements-handlers.min.js

1035 ms

lazyload.min.js

lazyload.min.js

1060 ms

complianz-logo.png

complianz-logo.png

552 ms

1.png

1.png

409 ms

roboto-normal-400.woff

roboto-normal-400.woff

528 ms

roboto-normal-500.woff

roboto-normal-500.woff

540 ms

roboto-normal-300.woff

roboto-normal-300.woff

580 ms

roboto-normal-100.woff

roboto-normal-100.woff

598 ms

roboto-normal-700.woff

roboto-normal-700.woff

633 ms

roboto-normal-900.woff

roboto-normal-900.woff

670 ms

fa-solid-900.woff

fa-solid-900.woff

1009 ms

fa-regular-400.woff

fa-regular-400.woff

800 ms

RobotoSlab-Black-1.ttf

RobotoSlab-Black-1.ttf

763 ms

RobotoSlab-SemiBold.ttf

RobotoSlab-SemiBold.ttf

779 ms

fa-brands-400.woff

fa-brands-400.woff

898 ms

eicons.woff

eicons.woff

851 ms

prettify.css

prettify.css

914 ms

Accessibility Review

complianz.io accessibility score

90

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

ARIA IDs are not unique

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

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

complianz.io SEO score

97

Search Engine Optimization Advices

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

complianz.io

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