Report Summary

  • 6

    Performance

    Renders faster than
    21% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

casyopea.com

Casyopea - магазин за натурална козметика, сапуни, масла, свещи

Page Load Speed

6.2 sec in total

First Response

522 ms

Resources Loaded

3.7 sec

Page Rendered

2 sec

casyopea.com screenshot

About Website

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

Casyopea е начин на живот, техники и познания в грижата за себе си, базирана на натурални съставки от природата. Натурални продукти от висококачествени съставки.

Visit casyopea.com

Key Findings

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

Performance Metrics

casyopea.com performance score

6

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

25/100

10%

LCP (Largest Contentful Paint)

Value36.6 s

0/100

25%

SI (Speed Index)

Value44.5 s

0/100

10%

TBT (Total Blocking Time)

Value12,500 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.414

24/100

15%

TTI (Time to Interactive)

Value45.6 s

0/100

10%

Network Requests Diagram

casyopea.com

522 ms

casyopea.com

1101 ms

css

50 ms

05dda842123bcf62a5b081edbb67a23b.css

474 ms

a3071bd65acc10ab069065d7d59192a4.js

715 ms

Our browser made a total of 56 requests to load all elements on the main page. We found that 64% of them (36 requests) were addressed to the original Casyopea.com, 9% (5 requests) were made to Connect.facebook.net and 5% (3 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Casyopea.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 529.4 kB (10%)

Content Size

5.1 MB

After Optimization

4.6 MB

In fact, the total size of Casyopea.com main page is 5.1 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 4.5 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 355.3 kB

  • Original 411.0 kB
  • After minification 411.0 kB
  • After compression 55.7 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 355.3 kB or 86% of the original size.

Image Optimization

-4%

Potential reduce by 173.3 kB

  • Original 4.5 MB
  • After minification 4.4 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. Casyopea images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 822 B

  • Original 108.7 kB
  • After minification 108.7 kB
  • After compression 107.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

-0%

Potential reduce by 0 B

  • Original 58.0 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.

Requests Breakdown

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

Requests Now

49

After Optimization

35

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

Accessibility Review

casyopea.com accessibility score

81

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.

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

Best Practices

casyopea.com best practices score

75

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

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

casyopea.com SEO score

92

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    BG

  • Language Claimed

    BG

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Casyopea.com can be misinterpreted by Google and other search engines. Our service has detected that Bulgarian is used on the page, and it matches the claimed language. Our system also found out that Casyopea.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

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