3.5 sec in total
302 ms
2 sec
1.2 sec
Visit gdata.pt now to see the best up-to-date G DATA content and also check out these interesting facts you probably never knew about gdata.pt
Nossos especialistas registram uma nova ameaça a cada 6 segundos - Deixe-se convencer pela reconhecida e premiada proteção contra vírus G DATA.
Visit gdata.ptWe analyzed Gdata.pt page load time and found that the first response time was 302 ms and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
gdata.pt performance score
name
value
score
weighting
Value1.9 s
86/100
10%
Value3.7 s
57/100
25%
Value3.5 s
89/100
10%
Value60 ms
100/100
30%
Value0.208
60/100
15%
Value4.2 s
86/100
10%
302 ms
510 ms
201 ms
288 ms
290 ms
Our browser made a total of 32 requests to load all elements on the main page. We found that all of those requests were addressed to Gdata.pt and no external sources were called. The less responsive or slowest element that took the longest time to load (690 ms) belongs to the original domain Gdata.pt.
Page size can be reduced by 41.0 kB (6%)
690.5 kB
649.6 kB
In fact, the total size of Gdata.pt main page is 690.5 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. 40% of websites need less resources to load. Images take 592.1 kB which makes up the majority of the site volume.
Potential reduce by 29.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 29.8 kB or 76% of the original size.
Potential reduce by 0 B
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. G DATA images are well optimized though.
Potential reduce by 9 B
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. This website has mostly compressed JavaScripts.
Potential reduce by 11.1 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. Gdata.pt needs all CSS files to be minified and compressed as it can save up to 11.1 kB or 22% of the original size.
Number of requests can be reduced by 16 (62%)
26
10
The browser has sent 26 CSS, Javascripts, AJAX and image requests in order to completely render the main page of G DATA. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
gdata.pt
302 ms
www.gdata.pt
510 ms
basic-styles.css
201 ms
gcon.css
288 ms
source-sans-pro.css
290 ms
alpaka-home.css
291 ms
momstypewriter.css
293 ms
gd-therefore-gdata.css
291 ms
gd-animated-circles.css
293 ms
main.css
382 ms
main-int.css
384 ms
main-consumer.css
384 ms
general-grid.css
390 ms
gd-pagenews.css
391 ms
logo_claim_white.png
533 ms
merged-1af48af311b651d5d575eb3f77469934.js
690 ms
Form.min.js
574 ms
countUp.js
529 ms
main.js
531 ms
award-grid.js
530 ms
G_DATA_Headline_WirSindBereit_White_PT.svg
531 ms
logo_claim_2016_white.png
571 ms
medium_face.png
599 ms
medium_stripe.png
270 ms
medium_bg.jpg
176 ms
home-campus-video.jpg
598 ms
home-why-gdata.jpg
459 ms
source-sans-pro-v13-latin-ext_latin-regular.woff
341 ms
source-sans-pro-v13-latin-ext_latin-300.woff
343 ms
source-sans-pro-v13-latin-ext_latin-600.woff
342 ms
gcon1-990.ttf
484 ms
lazysizes.js
147 ms
gdata.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
gdata.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
gdata.pt SEO score
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
PT
PT
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Gdata.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 Gdata.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.
gdata.pt
Open Graph description is not detected on the main page of G DATA. 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: