5.1 sec in total
414 ms
4.2 sec
477 ms
Click here to check amazing Corio CS content for Poland. Otherwise, check out these important facts you probably never knew about coriocs.pl
Na stronie naszego Centrum znajdziesz liczne szkolenia kosmetyczne organizowane w Poznaniu. Wejdź na stronę i zapoznaj się z najważniejszymi informacjami.
Visit coriocs.plWe analyzed Coriocs.pl page load time and found that the first response time was 414 ms and then it took 4.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
coriocs.pl performance score
name
value
score
weighting
Value10.5 s
0/100
10%
Value20.4 s
0/100
25%
Value22.4 s
0/100
10%
Value3,240 ms
2/100
30%
Value0.328
35/100
15%
Value19.2 s
2/100
10%
414 ms
666 ms
232 ms
233 ms
237 ms
Our browser made a total of 64 requests to load all elements on the main page. We found that 53% of them (34 requests) were addressed to the original Coriocs.pl, 16% (10 requests) were made to Static.xx.fbcdn.net and 13% (8 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Coriocs.pl.
Page size can be reduced by 182.2 kB (14%)
1.3 MB
1.1 MB
In fact, the total size of Coriocs.pl 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 1.1 MB which makes up the majority of the site volume.
Potential reduce by 19.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 19.5 kB or 67% of the original size.
Potential reduce by 26.4 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. Corio CS images are well optimized though.
Potential reduce by 124.9 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 124.9 kB or 63% of the original size.
Potential reduce by 11.3 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. Coriocs.pl needs all CSS files to be minified and compressed as it can save up to 11.3 kB or 75% of the original size.
Number of requests can be reduced by 27 (44%)
61
34
The browser has sent 61 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Corio CS. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
coriocs.pl
414 ms
www.coriocs.pl
666 ms
menu_style.css
232 ms
main_style.css
233 ms
lightbox.css
237 ms
prototype.js
476 ms
scriptaculous.js
234 ms
lightbox.js
236 ms
rotator.js
508 ms
jquery.js
623 ms
jquery.min.js
54 ms
popup.js
506 ms
plusone.js
68 ms
effects.js
245 ms
builder.js
129 ms
ga.js
74 ms
cb=gapi.loaded_0
66 ms
cb=gapi.loaded_1
18 ms
fastbutton
103 ms
logo.png
471 ms
baner5.jpg
534 ms
baner6.jpg
461 ms
baner7.jpg
356 ms
baner9.jpg
355 ms
navi.png
394 ms
phone2.png
473 ms
zapisz.png
503 ms
zostan.png
532 ms
kalendarz.png
629 ms
dyplomy.png
626 ms
dolacz.png
629 ms
dolaczfb.png
628 ms
gabinet.png
826 ms
mezoterapia.png
755 ms
przedluzanie.png
894 ms
manicure.png
1005 ms
makijaz.png
892 ms
iso-logo-corio.png
929 ms
baner-corio.png
2394 ms
button_close.png
1000 ms
__utm.gif
51 ms
postmessageRelay
72 ms
cb=gapi.loaded_0
39 ms
cb=gapi.loaded_1
40 ms
likebox.php
285 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
57 ms
3193398744-postmessagerelay.js
32 ms
rpc:shindig_random.js
41 ms
cb=gapi.loaded_0
4 ms
hDvwL1_H7g-.css
93 ms
56WNbrUYLbL.css
111 ms
q68gy-v_YMF.js
149 ms
FJmpeSpHpjS.js
179 ms
0wM5s1Khldu.js
147 ms
1bNoFZUdlYZ.js
148 ms
988934_827109783994974_6912521171797201254_n.jpg
128 ms
48154_507298545976101_1134460589_n.jpg
79 ms
1239557_840323016054389_5325917567930020158_n.jpg
189 ms
12316139_982421161831449_8666688021027813879_n.jpg
192 ms
12118968_435146966669850_1098118978835138819_n.jpg
55 ms
wL6VQj7Ab77.png
19 ms
s7jcwEQH7Sx.png
19 ms
I6-MnjEovm5.js
19 ms
pQrUxxo5oQp.js
35 ms
coriocs.pl 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.
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
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
coriocs.pl best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
coriocs.pl SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
PL
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Coriocs.pl can be misinterpreted by Google and other search engines. Our service has detected that Polish is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Coriocs.pl 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.
coriocs.pl
Open Graph description is not detected on the main page of Corio CS. 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: