10.1 sec in total
1.7 sec
6.9 sec
1.5 sec
Welcome to pocinho.pt homepage info - get ready to check Pocinho best content right away, or after learning these important things about pocinho.pt
Recently renovated 3 bedroom house for rental in the historic centre of Évora, Portugal. Évora's city center was considered World Heritage by UNESCO.
Visit pocinho.ptWe analyzed Pocinho.pt page load time and found that the first response time was 1.7 sec and then it took 8.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
pocinho.pt performance score
name
value
score
weighting
Value6.0 s
3/100
10%
Value16.7 s
0/100
25%
Value58.9 s
0/100
10%
Value54,910 ms
0/100
30%
Value0.194
63/100
15%
Value95.0 s
0/100
10%
1696 ms
112 ms
38 ms
24 ms
319 ms
Our browser made a total of 54 requests to load all elements on the main page. We found that 87% of them (47 requests) were addressed to the original Pocinho.pt, 6% (3 requests) were made to Fonts.gstatic.com and 4% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Pocinho.pt.
Page size can be reduced by 89.0 kB (3%)
3.2 MB
3.1 MB
In fact, the total size of Pocinho.pt main page is 3.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. 70% of websites need less resources to load. Images take 3.0 MB which makes up the majority of the site volume.
Potential reduce by 76.2 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 25.0 kB, which is 27% 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 76.2 kB or 83% of the original size.
Potential reduce by 12.6 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. Pocinho images are well optimized though.
Potential reduce by 36 B
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. This website has mostly compressed JavaScripts.
Potential reduce by 189 B
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. Pocinho.pt has all CSS files already compressed.
Number of requests can be reduced by 13 (28%)
47
34
The browser has sent 47 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pocinho. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 5 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
www.pocinho.pt
1696 ms
wp-emoji-release.min.js
112 ms
css
38 ms
css
24 ms
888e4295-1649223250.min.css
319 ms
color.css.php
544 ms
a5400b61-1648498405.min.css
206 ms
0fa8266c-1648498271.min.js
765 ms
cd39136b-1483560895.min.js
410 ms
js
53 ms
12872041-1648498405.min.js
393 ms
Telmo3.jpg
336 ms
Pocinho2_2.jpg
552 ms
Pocinho3.jpg
551 ms
Pocinho5.jpg
543 ms
Pocinho6.jpg
566 ms
Pocinho8.jpg
542 ms
Pocinho11.jpg
545 ms
Pocinho14_2.jpg
921 ms
Pocinho18.jpg
921 ms
Pocinho20.jpg
924 ms
Pocinho10_2.jpg
925 ms
Pocinho23_2.jpg
924 ms
Pocinho25.jpg
948 ms
Telmo1.jpg
948 ms
Paula_low.jpg
946 ms
Carol_low.jpg
1104 ms
Telmo2.jpg
950 ms
emma.jpg
949 ms
Screen-Shot-2017-01-05-at-22.52.32.png
1103 ms
Screen-Shot-2017-01-09-at-15.53.17.png
1105 ms
bec.png
1091 ms
Telmo4.jpg
1093 ms
Telmo6.jpg
1254 ms
Pocinho_logo.png
206 ms
Pocinho_logo@2x.png
210 ms
dummy.png
201 ms
paula.png
520 ms
candace.png
519 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aXw.woff
155 ms
close_calendar.png
124 ms
set-date.png
332 ms
zoom.png
331 ms
map-arrow.png
330 ms
17203081_1874075762814659_321226747206350142_n.jpg
717 ms
1403028_681117158660785_4727299258996667634_o.jpg
717 ms
alm-01.png
1062 ms
EvoraBikeHike.jpg
736 ms
back_top.png
330 ms
MwQsbh3o1vLImiwAVvYawgcf2eVer2q6bHU.woff
12 ms
MwQubh3o1vLImiwAVvYawgcf2eVeqlq-.woff
12 ms
ss-geomicons-squared.woff
361 ms
icomoon.woff
361 ms
gen_204
68 ms
pocinho.pt 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-hidden="true"] elements contain focusable descendents
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
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
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
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.
pocinho.pt 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
Missing source maps for large first-party JavaScript
pocinho.pt 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
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pocinho.pt can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Pocinho.pt 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.
pocinho.pt
Open Graph data is detected on the main page of Pocinho. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: