3.8 sec in total
457 ms
3.2 sec
192 ms
Click here to check amazing Casus content. Otherwise, check out these important facts you probably never knew about casus.biz
Visit casus.bizWe analyzed Casus.biz page load time and found that the first response time was 457 ms and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
casus.biz performance score
name
value
score
weighting
Value5.8 s
4/100
10%
Value8.8 s
1/100
25%
Value13.5 s
2/100
10%
Value2,630 ms
4/100
30%
Value0.002
100/100
15%
Value15.5 s
7/100
10%
457 ms
497 ms
116 ms
333 ms
448 ms
Our browser made a total of 76 requests to load all elements on the main page. We found that 68% of them (52 requests) were addressed to the original Casus.biz, 13% (10 requests) were made to Static.xx.fbcdn.net and 12% (9 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Casus.biz.
Page size can be reduced by 63.5 kB (65%)
97.6 kB
34.1 kB
In fact, the total size of Casus.biz main page is 97.6 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. 45% of websites need less resources to load. Javascripts take 52.9 kB which makes up the majority of the site volume.
Potential reduce by 31.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. This page needs HTML code to be minified as it can gain 12.6 kB, which is 32% 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 31.0 kB or 79% of the original size.
Potential reduce by 492 B
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. Casus images are well optimized though.
Potential reduce by 32.0 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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 32.0 kB or 60% of the original size.
Number of requests can be reduced by 33 (45%)
74
41
The browser has sent 74 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Casus. 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 from 4 to 1 for CSS and as a result speed up the page load time.
casus.biz
457 ms
www.casus.biz
497 ms
screen.css
116 ms
jquery.fancybox.css
333 ms
jquery.js
448 ms
jquery.cycle.js
231 ms
plugin.input.toggle.js
353 ms
jquery.fancybox.js
354 ms
jquery.fancybox.pack.js
350 ms
js
39 ms
casus.js
342 ms
logo.png
114 ms
ico1.png
114 ms
ico2.png
115 ms
ico3.png
122 ms
ico4.png
125 ms
ico5.png
123 ms
ico6.png
269 ms
logo2.png
268 ms
gtm.js
69 ms
bg_facebook.png
265 ms
phone.png
266 ms
underline.png
266 ms
fb.png
267 ms
mail.png
333 ms
menu.png
334 ms
line.png
336 ms
ban1.jpg
584 ms
button-big_2.png
354 ms
button-big_1.png
356 ms
ban2.jpg
664 ms
ban3.jpg
665 ms
ban4.jpg
557 ms
ban5.png
1642 ms
ban6.png
1533 ms
slider-a_left.png
679 ms
slider-a_right.png
702 ms
box.png
781 ms
button_2.png
790 ms
button_1.png
790 ms
button-small_2.png
807 ms
button-small_1.png
879 ms
button-empty_2.png
888 ms
button-empty_1.png
890 ms
wrapper-tips.png
914 ms
slider-c_left.png
980 ms
slider-c_right.png
989 ms
input_1.png
990 ms
likebox.php
120 ms
analytics.js
19 ms
collect
14 ms
input_2.png
951 ms
input_3.png
1011 ms
slider-b-bg.png
1239 ms
triangle.png
1013 ms
wrapper-footer.png
1060 ms
footer.png
1112 ms
410ucuAGgaJ.css
37 ms
tSbl8xBI27R.css
29 ms
1kPfZUdGrka.js
40 ms
Yuj_Y8xNH2C.js
39 ms
Mpe38fuBVZ2.js
27 ms
n8qIhCw3vMx.js
38 ms
11010569_968608209840499_3287766260164974471_n.png
26 ms
67011_156831381018190_2140993_n.jpg
13 ms
12705477_172733213096565_2539760271378591450_n.jpg
14 ms
1914212_101969739821253_303947_n.jpg
10 ms
3444_645198665621385_2623107415547495740_n.jpg
11 ms
12239690_882631771852359_7096674588459787882_n.jpg
13 ms
12688045_464629397059412_625949272270875062_n.jpg
12 ms
12717560_472452329610071_8692276653859653412_n.jpg
14 ms
10556510_318315341680270_6571404502175174928_n.jpg
14 ms
wL6VQj7Ab77.png
8 ms
s7jcwEQH7Sx.png
7 ms
VXcANLwwL5J.js
5 ms
AmlxWlqMvlv.js
5 ms
casus.biz accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
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
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
casus.biz best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
casus.biz SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
PL
PL
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Casus.biz can be misinterpreted by Google and other search engines. Our service has detected that Polish is used on the page, and it matches the claimed language. Our system also found out that Casus.biz 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.
casus.biz
Open Graph description is not detected on the main page of Casus. 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: