8.7 sec in total
341 ms
7.8 sec
503 ms
Visit prunis.com now to see the best up-to-date Prunis content and also check out these interesting facts you probably never knew about prunis.com
Location de vacances à 12 km de Sarlat-la-Canéda en Dordogne. Gîte de France 3 épis et agrément préfectoral 3 étoiles.
Visit prunis.comWe analyzed Prunis.com page load time and found that the first response time was 341 ms and then it took 8.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
prunis.com performance score
name
value
score
weighting
Value3.3 s
40/100
10%
Value4.3 s
42/100
25%
Value7.9 s
22/100
10%
Value810 ms
36/100
30%
Value0
100/100
15%
Value8.9 s
35/100
10%
341 ms
1307 ms
365 ms
662 ms
195 ms
Our browser made a total of 64 requests to load all elements on the main page. We found that 23% of them (15 requests) were addressed to the original Prunis.com, 20% (13 requests) were made to Google.com and 20% (13 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (5.5 sec) belongs to the original domain Prunis.com.
Page size can be reduced by 496.1 kB (42%)
1.2 MB
684.7 kB
In fact, the total size of Prunis.com main page is 1.2 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. 50% of websites need less resources to load. Javascripts take 682.5 kB which makes up the majority of the site volume.
Potential reduce by 8.1 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 1.9 kB, which is 17% 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 8.1 kB or 73% of the original size.
Potential reduce by 11.2 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. Prunis images are well optimized though.
Potential reduce by 475.7 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 475.7 kB or 70% of the original size.
Potential reduce by 1.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. Prunis.com needs all CSS files to be minified and compressed as it can save up to 1.1 kB or 77% of the original size.
Number of requests can be reduced by 19 (33%)
57
38
The browser has sent 57 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Prunis. 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.
prunis.com
341 ms
www.prunis.com
1307 ms
index.php
365 ms
index.php
662 ms
ja.rightcol.js
195 ms
system.css
168 ms
background.jpg
5505 ms
gite-dordogne-logo.png
362 ms
panorama-02.jpg
856 ms
bandeau-bois.png
485 ms
fleur-02.png
426 ms
fleur-01.png
435 ms
fleur-03.png
508 ms
maps
189 ms
arrow.png
562 ms
arrow2.png
567 ms
embed
455 ms
js
241 ms
init_embed.js
264 ms
common.js
109 ms
map.js
157 ms
google4.png
167 ms
overlay.js
73 ms
util.js
187 ms
onion.js
181 ms
search_impl.js
222 ms
StaticMapService.GetMapImage
377 ms
stats.js
124 ms
openhand_8_8.cur
72 ms
ViewportInfoService.GetViewportInfo
113 ms
ViewportInfoService.GetViewportInfo
66 ms
kh
335 ms
transparent.png
101 ms
kh
321 ms
controls.js
105 ms
kh
342 ms
kh
382 ms
kh
381 ms
kh
394 ms
kh
384 ms
kh
189 ms
kh
190 ms
kh
189 ms
vt
169 ms
vt
201 ms
vt
216 ms
vt
224 ms
vt
219 ms
vt
219 ms
vt
221 ms
vt
217 ms
vt
282 ms
vt
284 ms
vt
283 ms
vt
281 ms
css
216 ms
entity11.png
111 ms
mapcnt6.png
68 ms
tmapctrl.png
61 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
329 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
401 ms
Hgo13k-tfSpn0qi1SFdUfT8E0i7KZn-EPnyo3HZu7kw.woff
446 ms
d-6IYplOFocCacKzxwXSOD8E0i7KZn-EPnyo3HZu7kw.woff
450 ms
AuthenticationService.Authenticate
60 ms
prunis.com accessibility score
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
<frame> or <iframe> elements do not have a title
prunis.com 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
prunis.com SEO score
FR
FR
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Prunis.com can be misinterpreted by Google and other search engines. Our service has detected that French is used on the page, and it matches the claimed language. Our system also found out that Prunis.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.
prunis.com
Open Graph description is not detected on the main page of Prunis. 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: