40.9 sec in total
2.5 sec
38.2 sec
241 ms
Click here to check amazing Royalpanacea content for Turkey. Otherwise, check out these important facts you probably never knew about royalpanacea.com
Visit royalpanacea.comWe analyzed Royalpanacea.com page load time and found that the first response time was 2.5 sec and then it took 38.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there were 18 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
royalpanacea.com performance score
2499 ms
13414 ms
13299 ms
13227 ms
13546 ms
Our browser made a total of 130 requests to load all elements on the main page. We found that 65% of them (84 requests) were addressed to the original Royalpanacea.com, 25% (32 requests) were made to Royalpanacea.hweb.com and 3% (4 requests) were made to F.vimeocdn.com. The less responsive or slowest element that took the longest time to load (20.5 sec) belongs to the original domain Royalpanacea.com.
Page size can be reduced by 322.8 kB (54%)
597.3 kB
274.5 kB
In fact, the total size of Royalpanacea.com main page is 597.3 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. 40% of websites need less resources to load. Javascripts take 388.6 kB which makes up the majority of the site volume.
Potential reduce by 39.3 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 39.3 kB or 80% of the original size.
Potential reduce by 2.1 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. Royalpanacea images are well optimized though.
Potential reduce by 246.3 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 246.3 kB or 63% of the original size.
Potential reduce by 35.1 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. Royalpanacea.com needs all CSS files to be minified and compressed as it can save up to 35.1 kB or 81% of the original size.
Number of requests can be reduced by 24 (63%)
38
14
The browser has sent 38 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Royalpanacea. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
www.royalpanacea.com
2499 ms
language-selector.css
13414 ms
foundation-icons.css
13299 ms
normalize.css
13227 ms
foundation.min.css
13546 ms
styles.css
13471 ms
jquery-ui.min.css
20 ms
jquery-ui-timepicker-addon.min.css
13591 ms
css
39 ms
jquery.sidr.light.css
13859 ms
animate.css
14018 ms
drawingSVG.css
14241 ms
photostack.css
14266 ms
supersized.css
14302 ms
supersized.shutter.css
14538 ms
prettyPhoto.css
14745 ms
foundation-icons.css
15049 ms
jquery.bxslider.css
14956 ms
app.css
15010 ms
style.css
15156 ms
responsive.css
15208 ms
shortcodes.css
20486 ms
jquery.js
20486 ms
jquery-migrate.min.js
20486 ms
custom.modernizr.js
20487 ms
modernizr-2.7.1.min.js
20487 ms
hweb-search-pretty.js
689 ms
content-shortcodes.css
20495 ms
media-shortcodes.css
20496 ms
magnific-popup.css
20497 ms
galleries-shortcodes.css
20497 ms
jquery.form.min.js
20497 ms
scripts.js
20498 ms
core.min.js
20498 ms
datepicker.min.js
20499 ms
datepicker-tr.min.js
9 ms
jquery-ui-timepicker-addon.min.js
20497 ms
jquery-ui-timepicker-tr.js
20498 ms
widget.min.js
20498 ms
mouse.min.js
20498 ms
slider.min.js
20496 ms
button.min.js
15796 ms
jquery-ui-sliderAccess.js
15648 ms
foundation.min.js
15045 ms
app.min.js
15617 ms
classie.min.js
15502 ms
waypoints.min.js
15087 ms
smoothScroll.min.js
15331 ms
jquery.parallax-1.1.3.min.js
15305 ms
supersized.3.2.7.min.js
15365 ms
supersized.shutter.min.js
15552 ms
jquery.isotope.min.js
15479 ms
photostack.min.js
15309 ms
svganimations.min.js
15160 ms
jquery.timeago.min.js
15012 ms
tweetable.jquery.min.js
15297 ms
jquery.bxslider.min.js
15440 ms
jquery.prettyPhoto.min.js
15378 ms
jquery.sidr.min.js
15366 ms
main.js
10179 ms
navigation.js
10217 ms
skip-link-focus-fix.js
10476 ms
analytics.js
50 ms
search
453 ms
1x1
449 ms
comment-reply.min.js
10755 ms
foundation.min.js
10789 ms
script.js
10853 ms
wp-embed.min.js
10960 ms
sitepress.js
11013 ms
magnific-popup.js
11176 ms
swiper.js
11483 ms
galleries-shortcodes.js
11559 ms
wp-emoji-release.min.js
11610 ms
logo11.png
11745 ms
logok2.png
11702 ms
tr.png
11892 ms
en.png
12174 ms
de.png
12248 ms
royal065-274x170.jpg
12325 ms
collect
44 ms
131748670
81 ms
player.js
144 ms
player.css
121 ms
ga.js
72 ms
vuid.min.js
134 ms
__utm.gif
40 ms
proxy.html
53 ms
524130987.jpg
186 ms
widget-core.js
132 ms
jquery-1.9.1.js
300 ms
jquery-1.9.1.js
566 ms
jquery-1.9.1.js
395 ms
jquery-ui-1.10.3.custom.min.js
544 ms
jquery-ui-1.10.3.custom.min.js
139 ms
jquery-ui-1.10.3.custom.min.js
701 ms
jquery.ui.datepicker-tr.min.js
139 ms
settings
160 ms
jquery-ui-1.10.3.custom.min.css
132 ms
widget-theme.css
279 ms
widget-custom.css
512 ms
layouts
445 ms
phone-dark.png
155 ms
ouibounce.js
155 ms
icon-calendar.png
150 ms
ui-bg_flat_75_ffffff_40x100.png
152 ms
ouibounce.js
136 ms
jquery-ui-1.10.3.custom.min.css
152 ms
widget-hweb-search.css
315 ms
jquery-ui-1.10.3.custom.min.css
160 ms
widget-hweb-search.css
135 ms
royal045-274x170.jpg
4450 ms
royal036-274x170.jpg
4331 ms
royal029-274x170.jpg
4123 ms
royal026-274x170.jpg
4444 ms
royal011-274x170.jpg
4490 ms
s4-274x170.jpg
4473 ms
royal054.jpg
4436 ms
rez.png
4409 ms
www.royalpanacea.com
4521 ms
divider.png
4379 ms
gotop.png
4447 ms
settingsPopup
139 ms
settingsPopup
170 ms
hweb-free-reservation-tr.png
137 ms
hweb-arrow.png
274 ms
hweb-widget-eb-summer.jpg
271 ms
hweb-free-reservation-tr.png
150 ms
hweb-widget-eb-summer.jpg
638 ms
hweb-arrow.png
420 ms
royalpanacea.com SEO score
N/A
TR
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Royalpanacea.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is Turkish. Our system also found out that Royalpanacea.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.
royalpanacea.com
Open Graph description is not detected on the main page of Royalpanacea. 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: