4.8 sec in total
783 ms
3.8 sec
215 ms
Click here to check amazing GCP content for Portugal. Otherwise, check out these important facts you probably never knew about gcp.pt
O GCP, é uma referência no Desporto Nacional e pioneiro no conceito de Clube com finalidades desportivas, sociais e culturais.
Visit gcp.ptWe analyzed Gcp.pt page load time and found that the first response time was 783 ms and then it took 4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
gcp.pt performance score
name
value
score
weighting
Value1.7 s
93/100
10%
Value1.7 s
99/100
25%
Value6.2 s
44/100
10%
Value2,470 ms
4/100
30%
Value0.002
100/100
15%
Value7.5 s
47/100
10%
783 ms
360 ms
373 ms
367 ms
641 ms
Our browser made a total of 119 requests to load all elements on the main page. We found that 60% of them (71 requests) were addressed to the original Gcp.pt, 15% (18 requests) were made to Maps.googleapis.com and 8% (9 requests) were made to Gstatic.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Gcp.pt.
Page size can be reduced by 830.6 kB (47%)
1.8 MB
919.6 kB
In fact, the total size of Gcp.pt main page is 1.8 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. 50% of websites need less resources to load. Javascripts take 887.7 kB which makes up the majority of the site volume.
Potential reduce by 31.5 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 4.4 kB, which is 11% 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 31.5 kB or 78% of the original size.
Potential reduce by 36.4 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. GCP images are well optimized though.
Potential reduce by 616.3 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 616.3 kB or 69% of the original size.
Potential reduce by 146.3 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. Gcp.pt needs all CSS files to be minified and compressed as it can save up to 146.3 kB or 84% of the original size.
Number of requests can be reduced by 56 (51%)
110
54
The browser has sent 110 CSS, Javascripts, AJAX and image requests in order to completely render the main page of GCP. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 37 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
gcp.pt
783 ms
fontello.css
360 ms
animation.css
373 ms
styleFont.css
367 ms
bootstrap.min.css
641 ms
flexslider.css
380 ms
jtip.css
514 ms
site.css
723 ms
bootstrap-checkbox.css
610 ms
bootstrap-select.css
615 ms
WebResource.axd
634 ms
ScriptResource.axd
756 ms
ScriptResource.axd
851 ms
jquery-2.0.3.min.js
996 ms
bootstrap.min.js
799 ms
dropdown-on-hover-plugin.js
799 ms
jquery.flexslider.js
852 ms
jquery.realperson.css
922 ms
jquery.realperson.js
981 ms
jquery.equalheights.js
1064 ms
jquery.fancybox.js
1029 ms
jquery.fancybox.css
1094 ms
jquery.rwdImageMaps.min.js
1203 ms
jtip.js
1223 ms
jquery.slickhover.js
1238 ms
jquery.nivo.slider.pack.js
1280 ms
jquery.mousewheel-3.0.6.pack.js
1311 ms
funcoesJquery.js
1335 ms
bootstrap-checkbox.js
1442 ms
jquery.cookie.js
1467 ms
bootstrap-select.js
1577 ms
jquery.placeholder.js
1584 ms
lateral.jpg
979 ms
logo.gif
1009 ms
bt-siga-nos.png
1135 ms
telefone2.png
1133 ms
menu-riscos.png
1202 ms
43.jpg
1236 ms
44.jpg
1234 ms
34.jpg
1380 ms
225.jpg
1380 ms
223.jpg
1380 ms
224.jpg
1443 ms
1.jpg
1492 ms
2.jpg
1497 ms
3.jpg
1627 ms
4.jpg
1643 ms
anuncios-azul2.png
1710 ms
ms
132 ms
1.jpg
1533 ms
2.jpg
1547 ms
vagroln_0-webfont.woff
1448 ms
vag_rounded_bold-webfont.woff
1511 ms
embed
496 ms
fontello.woff
1453 ms
3.jpg
1519 ms
4.jpg
1523 ms
5.jpg
1555 ms
1Peq.jpg
1537 ms
7Peq.jpg
1499 ms
8Peq.jpg
1416 ms
9Peq.jpg
1527 ms
11Peq.jpg
1545 ms
logo-footer.gif
1556 ms
redes-footer.png
1535 ms
39.jpg
1508 ms
rs=ABjfnFW3NcDEAUOJhqBLkb_g7tp8huHPRg
42 ms
css
69 ms
js
96 ms
rs=ABjfnFVwLee7ilRNodS4pidryBsEUbxoyw
57 ms
bgr_botao_a.png
1301 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
151 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
152 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
198 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
222 ms
bgr_botao_left.png
1402 ms
rs=ABjfnFVwLee7ilRNodS4pidryBsEUbxoyw
68 ms
common.js
110 ms
map.js
142 ms
overlay.js
140 ms
22-blue-dot.png&filter=ff&scale=1.0
174 ms
util.js
174 ms
marker.js
135 ms
geocoder.js
131 ms
controls.js
130 ms
places_impl.js
168 ms
selection_2x-000.png
43 ms
gen204
90 ms
bgr_botao_right.png
1294 ms
separador-agenda-eventos.gif
1317 ms
analytics.js
32 ms
collect
53 ms
onion.js
64 ms
openhand_8_8.cur
104 ms
ViewportInfoService.GetViewportInfo
64 ms
stats.js
64 ms
kh
124 ms
kh
120 ms
kh
99 ms
kh
102 ms
transparent.png
65 ms
mapcnt6.png
51 ms
tmapctrl4.png
41 ms
vt
151 ms
vt
64 ms
vt
63 ms
vt
48 ms
vt
60 ms
viewer-icons001.png
78 ms
star4.png
85 ms
22-blue-dot.png&scale=1.0
66 ms
AuthenticationService.Authenticate
30 ms
MyMaps_Icons003.png
25 ms
mymaps_32.png
25 ms
v1_4593b7d7.png
29 ms
google-my-maps-logo-small-001.png
27 ms
vagroln_0-webfont.ttf
812 ms
vag_rounded_bold-webfont.ttf
709 ms
fontello.ttf
709 ms
gcp.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
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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
Heading elements are not in a sequentially-descending order
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.
gcp.pt best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
gcp.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
PT
N/A
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Gcp.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 Gcp.pt main page’s claimed encoding is iso-8859-1. 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.
gcp.pt
Open Graph description is not detected on the main page of GCP. 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: