Tools & Wizards About Us
cratia.com screenshot

Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

cratia.com

Home - Cratia

Page Load Speed

10.7 sec in total

First Response

371 ms

Resources Loaded

9.5 sec

Page Rendered

765 ms

cratia.com screenshot

About Website

Click here to check amazing Cratia content. Otherwise, check out these important facts you probably never knew about cratia.com

Cratia company provides professional services of registration, certification, pharmacovigilance of medical devices, equipment and medicines in the CIS countries.

Visit cratia.com

Key Findings

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

Performance Metrics

cratia.com performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

29/100

10%

LCP (Largest Contentful Paint)

Value9.2 s

1/100

25%

SI (Speed Index)

Value10.4 s

8/100

10%

TBT (Total Blocking Time)

Value780 ms

38/100

30%

CLS (Cumulative Layout Shift)

Value1.604

0/100

15%

TTI (Time to Interactive)

Value10.8 s

22/100

10%

Network Requests Diagram

cratia.com

371 ms

2313 ms

main.css

361 ms

bootstrap-grid-3.3.1.min.css

359 ms

style.min.css

384 ms

Our browser made a total of 94 requests to load all elements on the main page. We found that 89% of them (84 requests) were addressed to the original Cratia.com, 4% (4 requests) were made to Fonts.googleapis.com and 2% (2 requests) were made to Images.dmca.com. The less responsive or slowest element that took the longest time to load (2.7 sec) belongs to the original domain Cratia.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 162.3 kB (12%)

Content Size

1.3 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Cratia.com main page is 1.3 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. 45% of websites need less resources to load. Images take 649.3 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 104.2 kB

  • Original 123.6 kB
  • After minification 108.2 kB
  • After compression 19.4 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 15.4 kB, which is 12% 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 104.2 kB or 84% of the original size.

Image Optimization

-8%

Potential reduce by 50.7 kB

  • Original 649.3 kB
  • After minification 598.6 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. Cratia images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 3.7 kB

  • Original 450.5 kB
  • After minification 450.4 kB
  • After compression 446.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.

CSS Optimization

-3%

Potential reduce by 3.6 kB

  • Original 122.6 kB
  • After minification 122.6 kB
  • After compression 118.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. Cratia.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 73 (85%)

Requests Now

86

After Optimization

13

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

cratia.com

cratia.com

371 ms

2313 ms

main.css

main.css

361 ms

bootstrap-grid-3.3.1.min.css

bootstrap-grid-3.3.1.min.css

359 ms

style.min.css

style.min.css

384 ms

classic-themes.min.css

classic-themes.min.css

382 ms

styles.css

styles.css

382 ms

protect_style.css

protect_style.css

501 ms

dashicons.min.css

dashicons.min.css

826 ms

font-awesome.min.css

font-awesome.min.css

726 ms

icofont.min.css

icofont.min.css

866 ms

wpmm.css

wpmm.css

750 ms

wp-megamenu.css

wp-megamenu.css

753 ms

wpmm-featuresbox.css

wpmm-featuresbox.css

874 ms

wpmm-gridpost.css

wpmm-gridpost.css

1082 ms

style.basic.css

style.basic.css

1101 ms

style-simple-blue.css

style-simple-blue.css

1119 ms

style.css

style.css

1191 ms

css

css

32 ms

css

css

49 ms

jquery.min.js

jquery.min.js

1353 ms

jquery-migrate.min.js

jquery-migrate.min.js

1233 ms

wpmm-featuresbox.js

wpmm-featuresbox.js

1447 ms

wpmm-gridpost.js

wpmm-gridpost.js

1462 ms

css

css

52 ms

DMCABadgeHelper.min.js

DMCABadgeHelper.min.js

26 ms

all.css

all.css

1382 ms

iconmonstr-iconic-font.min.css

iconmonstr-iconic-font.min.css

1426 ms

animate.css

animate.css

1506 ms

jquery.fancybox.min.css

jquery.fancybox.min.css

1606 ms

owl.carousel.css

owl.carousel.css

1699 ms

css

css

19 ms

jquery-1.11.1.min.js

jquery-1.11.1.min.js

1844 ms

jquery.fancybox.min.js

jquery.fancybox.min.js

1748 ms

jquery.maskedinput.js

jquery.maskedinput.js

1781 ms

owl.carousel.min.js

owl.carousel.min.js

1856 ms

jquery-migrate-1.4.1.min.js

jquery-migrate-1.4.1.min.js

1979 ms

js

js

75 ms

wow.js

wow.js

2054 ms

main.js

main.js

2101 ms

map.js

map.js

2141 ms

index.js

index.js

2207 ms

index.js

index.js

2215 ms

api.js

api.js

40 ms

wpmm.js

wpmm.js

2342 ms

asl-prereq.js

asl-prereq.js

2170 ms

asl-core.js

asl-core.js

2201 ms

asl-results-vertical.js

asl-results-vertical.js

2230 ms

asl-autocomplete.js

asl-autocomplete.js

2310 ms

asl-load.js

asl-load.js

2318 ms

asl-wrapper.js

asl-wrapper.js

2324 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

2165 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

2181 ms

wp-polyfill.min.js

wp-polyfill.min.js

2208 ms

index.js

index.js

2225 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

2207 ms

dmca_protected_31_120.png

dmca_protected_31_120.png

26 ms

logo.png

logo.png

1722 ms

slider_new_2_1.jpg

slider_new_2_1.jpg

2000 ms

slider_new_1.jpg

slider_new_1.jpg

2159 ms

slider_new_3_2.jpg

slider_new_3_2.jpg

2195 ms

slider_new_4_2.jpg

slider_new_4_2.jpg

2046 ms

coutries-bg.jpg

coutries-bg.jpg

2055 ms

armeniya.png

armeniya.png

2078 ms

azerbaidzan.png

azerbaidzan.png

2354 ms

belorus.png

belorus.png

2391 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

19 ms

AkzidenzGroteskPro-LightCn.woff

AkzidenzGroteskPro-LightCn.woff

2633 ms

AkzidenzGroteskPro-Cn.woff

AkzidenzGroteskPro-Cn.woff

2614 ms

AkzidenzGroteskPro-MdCn.woff

AkzidenzGroteskPro-MdCn.woff

2606 ms

AkzidenzGroteskPro-BoldCn.woff

AkzidenzGroteskPro-BoldCn.woff

2551 ms

gruziya.png

gruziya.png

2356 ms

fa-brands-400.woff

fa-brands-400.woff

2632 ms

kazahstan.png

kazahstan.png

2604 ms

kirgizstan.png

kirgizstan.png

2547 ms

moldova.png

moldova.png

2563 ms

mongoliya.png

mongoliya.png

2488 ms

tadzikistan.png

tadzikistan.png

2455 ms

turkmenistan.png

turkmenistan.png

2638 ms

ukraine.png

ukraine.png

2606 ms

uzbekistan.png

uzbekistan.png

2548 ms

evrazia.png

evrazia.png

2570 ms

advantage1.png

advantage1.png

2591 ms

trust.png

trust.png

2570 ms

team_cl-e1580901577453.jpg

team_cl-e1580901577453.jpg

2635 ms

codex.png

codex.png

2615 ms

news30052024.jpg

news30052024.jpg

2543 ms

news01032024.jpg

news01032024.jpg

2672 ms

recaptcha__en.js

recaptcha__en.js

25 ms

pic_news072024.png

pic_news072024.png

2716 ms

pic_news5.jpg

pic_news5.jpg

2555 ms

pic_news5.jpg

pic_news5.jpg

2635 ms

pic_news6.jpg

pic_news6.jpg

2614 ms

footer-logo.png

footer-logo.png

2520 ms

Accessibility Review

cratia.com accessibility score

89

Accessibility Issues

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

Buttons do not have an accessible name

High

Links do not have a discernible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Best Practices

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

cratia.com SEO score

85

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

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

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

cratia.com

Open Graph data is detected on the main page of PARSED_DOMAIN, but there is no image specified in description. It would be a good idea for the website admin to select a nice image that can properly represent the website in Open Graph data, otherwise the first found image will be taken for this purpose and social media information block will look like this: