3.6 sec in total
427 ms
2.9 sec
216 ms
Click here to check amazing PCase content for Italy. Otherwise, check out these important facts you probably never knew about pcase.it
Il portale per la ricerca di immobili. Migliaia di case, locali commerciali e attività sia in vendita che affitto. Trova la casa giusta per te!
Visit pcase.itWe analyzed Pcase.it page load time and found that the first response time was 427 ms and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
pcase.it performance score
name
value
score
weighting
Value3.5 s
34/100
10%
Value5.5 s
19/100
25%
Value17.4 s
0/100
10%
Value36,320 ms
0/100
30%
Value0
100/100
15%
Value47.6 s
0/100
10%
427 ms
636 ms
718 ms
411 ms
730 ms
Our browser made a total of 77 requests to load all elements on the main page. We found that 5% of them (4 requests) were addressed to the original Pcase.it, 16% (12 requests) were made to Static.xx.fbcdn.net and 16% (12 requests) were made to Images.pcase.it. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Images.pcase.it.
Page size can be reduced by 251.4 kB (49%)
513.6 kB
262.1 kB
In fact, the total size of Pcase.it main page is 513.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. 65% of websites need less resources to load. Javascripts take 273.4 kB which makes up the majority of the site volume.
Potential reduce by 87.4 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 87.4 kB or 77% of the original size.
Potential reduce by 6.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. PCase images are well optimized though.
Potential reduce by 126.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 126.7 kB or 46% of the original size.
Potential reduce by 31.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. Pcase.it needs all CSS files to be minified and compressed as it can save up to 31.3 kB or 80% of the original size.
Number of requests can be reduced by 39 (54%)
72
33
The browser has sent 72 CSS, Javascripts, AJAX and image requests in order to completely render the main page of PCase. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 30 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
pcase.it
427 ms
www.pcase.it
636 ms
pcase.css
718 ms
jquery.fancybox-1.3.4.css
411 ms
jquery-1.7.2.min.js
730 ms
jquery.fancybox-1.3.4.pack.js
517 ms
cookies.js
421 ms
pcase.min.js
530 ms
plusone.js
97 ms
mapItaly.js
427 ms
show_ads.js
6 ms
pinit.js
6 ms
adsbygoogle.js
3 ms
css
26 ms
css
38 ms
cb=gapi.loaded_0
38 ms
logo_pcase.jpg
738 ms
PinExt.png
36 ms
home_sea.png
1091 ms
home_mountain.png
1089 ms
logo_desaturate.png
739 ms
ca-pub-6653677465163583.js
199 ms
zrt_lookup.html
196 ms
show_ads_impl.js
78 ms
loading_circle.gif
854 ms
Zd2E9abXLFGSr9G3YK2MsNxB8OB85xaNTJvVSB9YUjQ.woff
129 ms
b9QBgL0iMZfDSpmcXcE8nMrfajfqx5pse9BUPMmpr-I.woff
193 ms
-_Ctzj9b56b8RgXW8FArib3hpw3pgy2gAi-Ip7WPMi0.woff
194 ms
widgets.js
123 ms
pinit_main.js
117 ms
like.php
200 ms
ads
404 ms
likebox.php
237 ms
ga.js
125 ms
ajax_commenta.asp
379 ms
ajax_map.asp
243 ms
cb=gapi.loaded_1
46 ms
fastbutton
116 ms
osd.js
35 ms
pla
74 ms
button.831500944bc3eb7ea5276ccdc3f71d2e.js
69 ms
postmessageRelay
88 ms
cb=gapi.loaded_0
48 ms
cb=gapi.loaded_1
47 ms
vpc6VNjRPXV.js
102 ms
LVx-xkvaJ0b.png
112 ms
__utm.gif
22 ms
api.js
31 ms
core:rpc:shindig.random:shindig.sha1.js
97 ms
2536007149-postmessagerelay.js
62 ms
tweet_button.6a78875565a912489e9aef879c881358.it.html
19 ms
FbUd6dZS1Af.css
29 ms
dGJLq38YL-C.css
41 ms
_rx8naC75Dy.js
47 ms
x5F9OMjKyLw.js
85 ms
ICDbTSzjQEg.js
39 ms
TTCre3391I0.js
35 ms
map_area.png
362 ms
map.jpg
704 ms
map_slice.gif
670 ms
12341048_918179138230516_8676544207726443267_n.jpg
69 ms
12313973_918178238230606_1010411730348178802_n.jpg
29 ms
1506468_485312378274304_2480973578688510785_n.jpg
93 ms
12548907_915329011870091_1783379152174970582_n.jpg
142 ms
12742038_492899187579929_5941700640415312561_n.jpg
44 ms
10366031_316296628525344_558701022453485521_n.jpg
43 ms
12003265_901239299960843_815997092451137072_n.jpg
45 ms
10428439_391301034379175_7816526732021191285_n.jpg
38 ms
wL6VQj7Ab77.png
27 ms
s7jcwEQH7Sx.png
27 ms
condividi_googleplus.gif
494 ms
condividi_facebook.gif
498 ms
condividi_twitter.gif
696 ms
condividi_preferiti.gif
763 ms
jot
91 ms
I6-MnjEovm5.js
8 ms
vlXaquuXMrr.js
16 ms
pcase.it accessibility score
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
[aria-*] attributes do not match their roles
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
<frame> or <iframe> elements do not have a title
Form elements do not have associated labels
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
pcase.it best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
pcase.it 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
IT
N/A
WINDOWS-1252
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pcase.it can be misinterpreted by Google and other search engines. Our service has detected that Italian 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 Pcase.it main page’s claimed encoding is windows-1252. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
pcase.it
Open Graph description is not detected on the main page of PCase. 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: