6.5 sec in total
1.4 sec
4.8 sec
243 ms
Click here to check amazing Rcarganil content. Otherwise, check out these important facts you probably never knew about rcarganil.pt
Visit rcarganil.ptWe analyzed Rcarganil.pt page load time and found that the first response time was 1.4 sec and then it took 5.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
rcarganil.pt performance score
name
value
score
weighting
Value7.5 s
1/100
10%
Value14.3 s
0/100
25%
Value17.8 s
0/100
10%
Value360 ms
72/100
30%
Value0.179
68/100
15%
Value19.9 s
2/100
10%
1427 ms
312 ms
215 ms
215 ms
212 ms
Our browser made a total of 65 requests to load all elements on the main page. We found that 83% of them (54 requests) were addressed to the original Rcarganil.pt, 5% (3 requests) were made to S.gravatar.com and 3% (2 requests) were made to Staticxx.facebook.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Rcarganil.pt.
Page size can be reduced by 476.0 kB (55%)
872.8 kB
396.8 kB
In fact, the total size of Rcarganil.pt main page is 872.8 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. 45% of websites need less resources to load. Javascripts take 422.6 kB which makes up the majority of the site volume.
Potential reduce by 32.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 32.8 kB or 75% of the original size.
Potential reduce by 21.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. Rcarganil images are well optimized though.
Potential reduce by 305.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 305.8 kB or 72% of the original size.
Potential reduce by 116.2 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. Rcarganil.pt needs all CSS files to be minified and compressed as it can save up to 116.2 kB or 81% of the original size.
Number of requests can be reduced by 40 (63%)
64
24
The browser has sent 64 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Rcarganil. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and from 17 to 1 for CSS and as a result speed up the page load time.
www.rcarganil.pt
1427 ms
style.css
312 ms
gallery-bank.css
215 ms
prettyPhoto.css
215 ms
styles.css
212 ms
sidebar-login.css
213 ms
css
23 ms
app.css
314 ms
jetpack.css
519 ms
featured-post.css
313 ms
jquery.js
726 ms
jquery-migrate.min.js
315 ms
jquery.bgiframe.js
416 ms
jquery.tooltip.min.js
416 ms
jquery.masonry.min.js
417 ms
isotope.pkgd.js
622 ms
imgLiquid.js
520 ms
jquery.prettyPhoto.js
622 ms
jquery.blockUI.min.js
521 ms
sidebar-login.min.js
620 ms
jquery.cycle.all.2.72.js
727 ms
counter.css
623 ms
dmsguestbook.css
723 ms
thickbox.css
724 ms
events-calendar.css
724 ms
thickbox.js
532 ms
jquery.form.min.js
734 ms
scripts.js
632 ms
devicepx-jetpack.js
6 ms
gprofiles.js
54 ms
wpgroho.js
631 ms
jquery.cycle.all.min.js
736 ms
simplecatch_slider.js
634 ms
simplecatch_search.js
632 ms
wp-embed.min.js
734 ms
selectivizr.js
734 ms
e-201611.js
6 ms
978.css
633 ms
wp-emoji-release.min.js
221 ms
ec-tooltips.css
107 ms
1337.png
148 ms
header-top-footer-bg.jpg
147 ms
cropped-rca_logo2-01.png
147 ms
emissao_online.png
148 ms
social-profile.png
213 ms
Untitled-1-976x313.jpg
452 ms
pdf.png
213 ms
QN4A6402-300x200.jpg
221 ms
DISCOS-PEDIDOS.jpg
425 ms
livro-visitas.jpg
317 ms
ul-bg.png
312 ms
timthumb.php
351 ms
timthumb.php
348 ms
timthumb.php
431 ms
blockquote-bg.jpg
420 ms
logo1%C2%AA.png
453 ms
switch.png
454 ms
sdk.js
161 ms
hovercard.css
94 ms
services.css
95 ms
loadingAnimation.gif
479 ms
g.gif
89 ms
140 ms
xd_arbiter.php
143 ms
xd_arbiter.php
265 ms
rcarganil.pt 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
Buttons do not have an accessible name
Document doesn't have a <title> element
<frame> or <iframe> elements do not have a title
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
rcarganil.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
rcarganil.pt SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Document doesn't have a <title> element
Image elements do not have [alt] attributes
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
PT
PT
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Rcarganil.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 Rcarganil.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.
rcarganil.pt
Open Graph description is not detected on the main page of Rcarganil. 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: