8.7 sec in total
1.2 sec
7.3 sec
291 ms
Click here to check amazing Coopor Pai content for Portugal. Otherwise, check out these important facts you probably never knew about coopor.pai.pt
A Coopor em Portalegre é especialista na produção de azeite São Mamede, proveniente da Serra de São Mamede no Alto Alentejo. Contacte-nos!
Visit coopor.pai.ptWe analyzed Coopor.pai.pt page load time and found that the first response time was 1.2 sec and then it took 7.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
coopor.pai.pt performance score
name
value
score
weighting
Value1.3 s
98/100
10%
Value3.1 s
74/100
25%
Value3.1 s
93/100
10%
Value120 ms
97/100
30%
Value0.341
33/100
15%
Value7.8 s
44/100
10%
1190 ms
337 ms
250 ms
234 ms
343 ms
Our browser made a total of 171 requests to load all elements on the main page. We found that 19% of them (32 requests) were addressed to the original Coopor.pai.pt, 15% (25 requests) were made to Static.xx.fbcdn.net and 11% (19 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (3 sec) relates to the external source Img.pai.pt.
Page size can be reduced by 1.0 MB (35%)
2.9 MB
1.9 MB
In fact, the total size of Coopor.pai.pt main page is 2.9 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. 60% of websites need less resources to load. Images take 1.8 MB which makes up the majority of the site volume.
Potential reduce by 63.8 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 63.8 kB or 77% of the original size.
Potential reduce by 144.9 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. Coopor Pai images are well optimized though.
Potential reduce by 703.8 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 703.8 kB or 79% of the original size.
Potential reduce by 99.8 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. Coopor.pai.pt needs all CSS files to be minified and compressed as it can save up to 99.8 kB or 88% of the original size.
Number of requests can be reduced by 62 (36%)
170
108
The browser has sent 170 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Coopor Pai. 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 13 to 1 for CSS and as a result speed up the page load time.
coopor.pai.pt
1190 ms
yui-common-styles.css
337 ms
app-common-styles.css
250 ms
lp-base-styles.css
234 ms
theme-default.css
343 ms
yui-common-scripts.js
546 ms
app-common-scripts.js
754 ms
lp-base-scripts.js
568 ms
tracking.js
652 ms
SAPOMapsAPI.js
807 ms
edit-opening-hours-styles.css
566 ms
edit-opening-hours-scripts.js
627 ms
sso.js
318 ms
modernizr.js
845 ms
bingmap7.css
543 ms
yellowMapIframe.js
264 ms
Style.css
107 ms
print-styles.css
141 ms
bc849069-c476-4c61-ad3a-97bd294d5008_LARGE.png
3038 ms
background.jpg
745 ms
50723a2f-7dc4-4386-a7f2-453ad1781820_LARGE.jpg
1750 ms
87c2485e-38ec-42b0-a501-9e1178c202b6_LARGE.jpg
1084 ms
60befe3d-7915-4728-b3e0-3d3f9c1b77c2_LOGO.png
704 ms
icons-links.gif
216 ms
ico_share.png
217 ms
rating_star_white.gif
183 ms
preload.gif
171 ms
landingpage-sprites.png
837 ms
facebook_button.png
305 ms
searchbarbg.jpg
313 ms
footerSearchBarBtnBg.jpg
422 ms
wtid.js
48 ms
directions7.js
365 ms
index.ajah;jsessionid=DD032DF21DBED95B7564BD437574BFE6
429 ms
009.png
628 ms
010.png
630 ms
010.png
763 ms
009.png
346 ms
008.png
343 ms
010.png
626 ms
008.png
525 ms
mapas_escala.gif
342 ms
309.jpeg
543 ms
all.js
271 ms
loadBooking.ajah;jsessionid=DD032DF21DBED95B7564BD437574BFE6
323 ms
checkMobile.ajaj;jsessionid=DD032DF21DBED95B7564BD437574BFE6
408 ms
ratings.ajah;jsessionid=DD032DF21DBED95B7564BD437574BFE6
405 ms
numberOfReviews.ajah;jsessionid=DD032DF21DBED95B7564BD437574BFE6
442 ms
loadBookingForWT.ajah;jsessionid=DD032DF21DBED95B7564BD437574BFE6
487 ms
106.jpeg
530 ms
008.jpeg
372 ms
309.jpeg
475 ms
310.jpeg
474 ms
106.jpeg
485 ms
107.jpeg
498 ms
3048cba1287c3ec9f63a5f4faaf3aea375cf2ad5add677a2bc4d24b43aec6337.png
292 ms
mapas_escalaw.gif
293 ms
619f74c2eda1e2d9d500e02151fcd9583f16f7ba837aa064325a20ceee587490.png
292 ms
arrow_up.gif
293 ms
arrow_left.gif
293 ms
arrow_center.gif
388 ms
arrow_right.gif
387 ms
arrow_down.gif
388 ms
plus.gif
388 ms
minus.gif
390 ms
zoom_point.gif
390 ms
zoom_select.gif
487 ms
status_btn.png
491 ms
zoom_circle.png
491 ms
zoom_in.png
490 ms
zoom_slide.png
493 ms
zoom_out.png
494 ms
010.jpeg
742 ms
009.png
564 ms
008.png
574 ms
010.jpeg
595 ms
009.jpeg
462 ms
008.jpeg
470 ms
311.jpeg
899 ms
310.jpeg
886 ms
108.jpeg
1020 ms
107.jpeg
1008 ms
009.png
565 ms
010.jpeg
460 ms
009.jpeg
467 ms
311.jpeg
465 ms
108.jpeg
523 ms
009.png
341 ms
008.jpeg
569 ms
009.jpeg
361 ms
310.jpeg
526 ms
309.jpeg
469 ms
311.jpeg
690 ms
107.jpeg
763 ms
106.jpeg
803 ms
108.jpeg
906 ms
010.png
271 ms
008.png
559 ms
009.jpeg
453 ms
010.jpeg
357 ms
008.jpeg
455 ms
311.jpeg
672 ms
310.jpeg
776 ms
309.jpeg
870 ms
108.jpeg
908 ms
107.jpeg
996 ms
106.jpeg
1013 ms
008.png
559 ms
010.png
620 ms
009.jpeg
358 ms
008.jpeg
358 ms
010.jpeg
359 ms
310.jpeg
694 ms
311.jpeg
779 ms
309.jpeg
774 ms
107.jpeg
793 ms
108.jpeg
997 ms
106.jpeg
1055 ms
124 ms
xd_arbiter.php
207 ms
xd_arbiter.php
423 ms
dcs.gif
40 ms
wa.gif
422 ms
plusone.js
64 ms
checkLoggedIn.ajaj;jsessionid=DD032DF21DBED95B7564BD437574BFE6
114 ms
cb=gapi.loaded_0
5 ms
like_box.php
252 ms
E6teJbut7Oz.css
286 ms
KJtsWU0X327.css
355 ms
SjGvcmqWmCE.css
423 ms
XTTgN4H9kuN.css
555 ms
EWhhEkcBPae.css
570 ms
XCdv7aD40Gm.js
622 ms
lnwXDK64af8.js
640 ms
mn6tHWuLI-Y.js
491 ms
x8BMxYCqTb9.js
493 ms
QKy94bWvcbp.js
580 ms
5paioeCYCa7.js
579 ms
wRXOQ26LQ1k.js
688 ms
UMeIUxuSxxa.js
824 ms
604064_498042523549545_1518555110_n.png
479 ms
69747_498039470216517_981119208_n.png
563 ms
12360335_565633560254197_6889109095058483847_n.jpg
705 ms
1010358_1654503224799735_3323377897610011912_n.jpg
711 ms
12347705_185398418474983_6690200937248414110_n.jpg
674 ms
11990472_10204845608641085_6243199747001068464_n.jpg
732 ms
12734244_163671677346159_5188212069160538692_n.jpg
719 ms
12523993_777917135671971_5066178226922793611_n.jpg
706 ms
10858452_1007539229271751_4980614813172585931_n.jpg
867 ms
10730903_859326744087786_121184912040216950_n.jpg
848 ms
10629673_859326110754516_6365269728405009591_n.jpg
848 ms
10410847_847055945314866_1625101081287803545_n.jpg
896 ms
10419033_847056965314764_377864329367895425_n.jpg
946 ms
16383_847056395314821_8040680332641688823_n.jpg
871 ms
1011086_847055561981571_2926004446360114118_n.jpg
1018 ms
1970674_845122875508173_4131583896070653683_n.jpg
975 ms
10649836_845122788841515_2529234018800408340_n.jpg
1019 ms
10382447_845123095508151_450078498277602271_n.jpg
982 ms
10612580_845122225508238_4631420272011349413_n.jpg
1181 ms
wL6VQj7Ab77.png
69 ms
s7jcwEQH7Sx.png
70 ms
mbF8ssTVP_5.png
71 ms
Fe6g47SXw-8.png
73 ms
L5AOQ9vzKfo.png
74 ms
oULnqcel5Nm.png
71 ms
q2ibvFgTxmh.png
134 ms
A2JLtDOGyCJ.png
139 ms
pimRBh7B6ER.png
137 ms
Fy3hs8lKW0M.png
135 ms
VXcANLwwL5J.js
70 ms
50Trs1RKgUY.js
71 ms
coopor.pai.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-*] attributes do not match their roles
[role]s are not contained by their required parent element
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
Form elements do not have associated labels
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.
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.
coopor.pai.pt 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
Page has valid source maps
coopor.pai.pt SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
PT
PT
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Coopor.pai.pt can be misinterpreted by Google and other search engines. Our service has detected that Portuguese is used on the page, and it matches the claimed language. Our system also found out that Coopor.pai.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.
coopor.pai.pt
Open Graph data is detected on the main page of Coopor Pai. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: