Report Summary

  • 30

    Performance

    Renders faster than
    50% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

caudex.com

Home

Page Load Speed

2.8 sec in total

First Response

34 ms

Resources Loaded

930 ms

Page Rendered

1.8 sec

caudex.com screenshot

About Website

Visit caudex.com now to see the best up-to-date Caudex content and also check out these interesting facts you probably never knew about caudex.com

Visit caudex.com

Key Findings

We analyzed Caudex.com page load time and found that the first response time was 34 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

caudex.com performance score

30

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

60/100

10%

LCP (Largest Contentful Paint)

Value8.8 s

1/100

25%

SI (Speed Index)

Value9.9 s

10/100

10%

TBT (Total Blocking Time)

Value1,100 ms

23/100

30%

CLS (Cumulative Layout Shift)

Value0.031

100/100

15%

TTI (Time to Interactive)

Value15.5 s

7/100

10%

Network Requests Diagram

caudex.com

34 ms

caudex.com

158 ms

anon-5MedSitesCDX-cm0yx6g62000gltqg4pjqbyeh.css

149 ms

otSDKStub.js

39 ms

player.js

44 ms

Our browser made a total of 48 requests to load all elements on the main page. We found that 4% of them (2 requests) were addressed to the original Caudex.com, 81% (39 requests) were made to Fcb-prod.s3.us-east-1.amazonaws.com and 6% (3 requests) were made to Cdn.cookielaw.org. The less responsive or slowest element that took the longest time to load (501 ms) relates to the external source Fcb-prod.s3.us-east-1.amazonaws.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 280.8 kB (7%)

Content Size

4.2 MB

After Optimization

3.9 MB

In fact, the total size of Caudex.com main page is 4.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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 3.1 MB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 277.3 kB

  • Original 308.9 kB
  • After minification 294.7 kB
  • After compression 31.5 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 277.3 kB or 90% of the original size.

Image Optimization

-0%

Potential reduce by 2.9 kB

  • Original 3.1 MB
  • After minification 3.1 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. Caudex images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 419 B

  • Original 657.6 kB
  • After minification 657.6 kB
  • After compression 657.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 216 B

  • Original 77.2 kB
  • After minification 77.2 kB
  • After compression 76.9 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. Caudex.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 5 (14%)

Requests Now

36

After Optimization

31

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

Accessibility Review

caudex.com accessibility score

93

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 input fields do not have accessible names

High

ARIA toggle fields do not have accessible names

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

<frame> or <iframe> elements do not have a title

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

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

SEO Factors

caudex.com SEO score

83

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

    EN

  • Language Claimed

    EN

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Caudex.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 Caudex.com main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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