3.5 sec in total
446 ms
2.7 sec
326 ms
Visit cces.pt now to see the best up-to-date CCES content and also check out these interesting facts you probably never knew about cces.pt
Centro Clínico Especialidades de Saúde
Visit cces.ptWe analyzed Cces.pt page load time and found that the first response time was 446 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
cces.pt performance score
name
value
score
weighting
Value5.7 s
5/100
10%
Value21.8 s
0/100
25%
Value12.7 s
3/100
10%
Value920 ms
30/100
30%
Value0.204
61/100
15%
Value23.1 s
1/100
10%
446 ms
225 ms
223 ms
224 ms
210 ms
Our browser made a total of 68 requests to load all elements on the main page. We found that 81% of them (55 requests) were addressed to the original Cces.pt, 4% (3 requests) were made to V2.zopim.com and 4% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Cces.pt.
Page size can be reduced by 332.1 kB (23%)
1.4 MB
1.1 MB
In fact, the total size of Cces.pt main page is 1.4 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. 65% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 20.9 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 6.7 kB, which is 26% 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 20.9 kB or 81% of the original size.
Potential reduce by 73.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. CCES images are well optimized though.
Potential reduce by 190.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 190.7 kB or 71% of the original size.
Potential reduce by 46.9 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. Cces.pt needs all CSS files to be minified and compressed as it can save up to 46.9 kB or 83% of the original size.
Number of requests can be reduced by 26 (46%)
57
31
The browser has sent 57 CSS, Javascripts, AJAX and image requests in order to completely render the main page of CCES. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
cces.pt
446 ms
shCore.css
225 ms
shThemeDefault.css
223 ms
demo.css
224 ms
flexslider.css
210 ms
modernizr.js
225 ms
fonts.css
208 ms
default.css
311 ms
component.css
413 ms
modernizr.custom.js
338 ms
jquery.min.js
59 ms
menu.css
322 ms
menu.js
338 ms
jquery.js
527 ms
jquery-1.8.2.min.js
5 ms
default.css
439 ms
nivo-slider.css
437 ms
style.css
438 ms
css.css
439 ms
css
28 ms
jquery.dlmenu.js
515 ms
jquery-1.9.0.min.js
475 ms
jquery.nivo.slider.js
590 ms
jquery.flexslider.js
591 ms
shCore.js
476 ms
shBrushXml.js
587 ms
shBrushJScript.js
587 ms
jquery.easing.js
589 ms
jquery.mousewheel.js
590 ms
demo.js
637 ms
css
14 ms
analytics.js
21 ms
fundo.jpg
284 ms
logo.png
210 ms
espaco.png
209 ms
FACILIDADES.png
210 ms
MARCACOES.png
210 ms
COMOCHEGAR.png
281 ms
big_1448547901.jpg
431 ms
big_1448393852.jpg
599 ms
big_1454427299.jpg
745 ms
big_1448392448.jpg
514 ms
big_1448368519.jpg
586 ms
big_1448369720.jpg
586 ms
big_1448538488.jpg
735 ms
1.jpg
615 ms
2.jpg
688 ms
3.jpg
690 ms
thumb_1448626312.jpg
700 ms
thumb_1448626294.jpg
717 ms
thumb_1448626280.jpg
791 ms
thumb_1448626273.jpg
791 ms
thumb_1448626258.jpg
801 ms
thumb_1448626248.jpg
819 ms
thumb_1448626235.jpg
837 ms
acordos.png
1267 ms
5star.png
892 ms
telefone.png
887 ms
widget_v2.134.js
23 ms
7XUFZ5tgS-tD6QamInJTcdGU7DQ8I6RFMlK0vgclk7w.woff
107 ms
anMUvcNT0H1YN4FII8wprx7IBmrqA5IG9z8WNe77b9o.woff
108 ms
anMUvcNT0H1YN4FII8wpr0bathaSTBR2c4i13_wzlb0.woff
108 ms
collect
90 ms
__$$__stringtable_lang_pt.js
31 ms
avatar_simple_visitor.png
90 ms
arrows.png
533 ms
aL63HcygAAVYuCCsAAA==
1 ms
flexslider-icon.woff
518 ms
cces.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.
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 IDs are not unique
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
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.
cces.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
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
Issues were logged in the Issues panel in Chrome Devtools
cces.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
Tap targets are not sized appropriately
PT
N/A
N/A
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Cces.pt can be misinterpreted by Google and other search engines. Our service has detected that Portuguese 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 Cces.pt main page’s claimed encoding is . 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.
cces.pt
Open Graph description is not detected on the main page of CCES. 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: