3.7 sec in total
900 ms
2.6 sec
223 ms
Welcome to cap.pt homepage info - get ready to check CAP best content for Portugal right away, or after learning these important things about cap.pt
A CAP iniciou em 1975 um percurso de defesa e representação dos agricultores de Portugal perante as instituições oficiais, nacionais e europeias, assim como perante a sociedade civil em geral. A CAP é...
Visit cap.ptWe analyzed Cap.pt page load time and found that the first response time was 900 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
cap.pt performance score
name
value
score
weighting
Value4.0 s
23/100
10%
Value9.2 s
1/100
25%
Value12.1 s
3/100
10%
Value2,940 ms
3/100
30%
Value0.01
100/100
15%
Value15.4 s
7/100
10%
900 ms
313 ms
330 ms
218 ms
219 ms
Our browser made a total of 49 requests to load all elements on the main page. We found that 94% of them (46 requests) were addressed to the original Cap.pt, 6% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (988 ms) belongs to the original domain Cap.pt.
Page size can be reduced by 303.9 kB (58%)
526.9 kB
222.9 kB
In fact, the total size of Cap.pt main page is 526.9 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. 15% of websites need less resources to load. Javascripts take 210.0 kB which makes up the majority of the site volume.
Potential reduce by 52.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 52.8 kB or 81% of the original size.
Potential reduce by 15.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. CAP images are well optimized though.
Potential reduce by 149.5 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 149.5 kB or 71% of the original size.
Potential reduce by 86.5 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. Cap.pt needs all CSS files to be minified and compressed as it can save up to 86.5 kB or 82% of the original size.
Number of requests can be reduced by 20 (42%)
48
28
The browser has sent 48 CSS, Javascripts, AJAX and image requests in order to completely render the main page of CAP. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for CSS and as a result speed up the page load time.
cap.pt
900 ms
style.css
313 ms
style.css
330 ms
style.css
218 ms
style.css
219 ms
template.css
554 ms
template.css
431 ms
css1b7fa.css
441 ms
css35e02.css
332 ms
css06e47.css
416 ms
css13739.css
547 ms
css5a54c.css
445 ms
js06cfe.js
988 ms
visao2020.png
426 ms
REDAP.png
536 ms
conselho_presidentes_2015_.png
536 ms
cultiva_o_teu_futuro_5.png
544 ms
projeto_dar_receber.png
441 ms
protocolos_bancos.jpg
447 ms
congresso_cap-videos.png
532 ms
banner-manual-cap-otoc.png
548 ms
emprego_e_formacao_agricola-banner.png
555 ms
saa.png
641 ms
higiene_na_producao_primaria_de_hortofruticolas_frescos.png
760 ms
Revista-do-Agricultor.png
646 ms
Noticias-CAP.png
658 ms
Jornalinho-do-Campo.png
662 ms
wine_in_moderation-protocolo.png
669 ms
icnf-portugal_sem_fogos.jpg
751 ms
revista_de_vinhos.jpg
756 ms
idigital-servico.jpg
768 ms
isip-servico.jpg
776 ms
ajuda_cap_pt.jpg
782 ms
poph-qren-fse.png
858 ms
icon-min.gif
112 ms
icon-max.gif
112 ms
logo.gif
124 ms
icon-search.gif
112 ms
but-bg.gif
124 ms
mainnav-bg.gif
152 ms
mainnav-active.gif
179 ms
arrow3.png
179 ms
dot.gif
138 ms
dot.gif
139 ms
ga.js
9 ms
popup.html
108 ms
tooltip.html
109 ms
__utm.gif
12 ms
__utm.gif
3 ms
cap.pt accessibility score
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
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
Image elements do not have [alt] attributes
Links do not have a discernible name
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.
cap.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
Missing source maps for large first-party JavaScript
cap.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 Cap.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 Cap.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.
cap.pt
Open Graph description is not detected on the main page of CAP. 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: