Tools & Wizards About Us
gdb.net screenshot

Report Summary

  • 43

    Performance

    Renders faster than
    62% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

gdb.net

GDB | Safe Media

Page Load Speed

5 sec in total

First Response

816 ms

Resources Loaded

3.3 sec

Page Rendered

867 ms

gdb.net screenshot

About Website

Welcome to gdb.net homepage info - get ready to check GDB best content right away, or after learning these important things about gdb.net

GDB is a global Adtech company that delivers comprehensive digital media solutions, empowering brands to communicate effectively with their audiences, ensuring quality, safety, privacy, and transparen...

Visit gdb.net

Key Findings

We analyzed Gdb.net page load time and found that the first response time was 816 ms and then it took 4.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

gdb.net performance score

43

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

57/100

10%

LCP (Largest Contentful Paint)

Value5.1 s

25/100

25%

SI (Speed Index)

Value5.9 s

49/100

10%

TBT (Total Blocking Time)

Value940 ms

30/100

30%

CLS (Cumulative Layout Shift)

Value0.068

96/100

15%

TTI (Time to Interactive)

Value9.6 s

29/100

10%

Network Requests Diagram

gdb.net

816 ms

custom.css

124 ms

styles.css

182 ms

ivory-search.min.css

184 ms

css

32 ms

Our browser made a total of 63 requests to load all elements on the main page. We found that 70% of them (44 requests) were addressed to the original Gdb.net, 19% (12 requests) were made to Fonts.gstatic.com and 5% (3 requests) were made to Cmpdelivery.gdb.net. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Cmpcdn.gdb.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 510.9 kB (11%)

Content Size

4.8 MB

After Optimization

4.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Gdb.net main page is 4.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. Images take 3.9 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 129.4 kB

  • Original 157.2 kB
  • After minification 154.6 kB
  • After compression 27.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 129.4 kB or 82% of the original size.

Image Optimization

-1%

Potential reduce by 23.1 kB

  • Original 3.9 MB
  • After minification 3.9 MB

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. GDB images are well optimized though.

JavaScript Optimization

-51%

Potential reduce by 357.5 kB

  • Original 700.5 kB
  • After minification 700.5 kB
  • After compression 343.0 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 357.5 kB or 51% of the original size.

CSS Optimization

-10%

Potential reduce by 848 B

  • Original 8.7 kB
  • After minification 8.7 kB
  • After compression 7.8 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. Gdb.net has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 34 (69%)

Requests Now

49

After Optimization

15

  • Images
  • JavaScript
  • CSS

The browser has sent 49 CSS, Javascripts, AJAX and image requests in order to completely render the main page of GDB. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

gdb.net

gdb.net

816 ms

custom.css

custom.css

124 ms

styles.css

styles.css

182 ms

ivory-search.min.css

ivory-search.min.css

184 ms

css

css

32 ms

css

css

19 ms

ivory-ajax-search.min.css

ivory-ajax-search.min.css

150 ms

jquery.min.js

jquery.min.js

152 ms

jquery-migrate.min.js

jquery-migrate.min.js

183 ms

jquery.mask.js

jquery.mask.js

188 ms

master.js

master.js

189 ms

hooks.min.js

hooks.min.js

190 ms

i18n.min.js

i18n.min.js

203 ms

index.js

index.js

203 ms

index.js

index.js

248 ms

scripts.min.js

scripts.min.js

376 ms

jquery.fitvids.js

jquery.fitvids.js

247 ms

jquery.mobile.js

jquery.mobile.js

250 ms

common.js

common.js

251 ms

ivory-search.min.js

ivory-search.min.js

256 ms

ivory-ajax-search.min.js

ivory-ajax-search.min.js

372 ms

motion-effects.js

motion-effects.js

437 ms

sticky-elements.js

sticky-elements.js

459 ms

cmp.php

cmp.php

432 ms

cmp_en.min.js

cmp_en.min.js

1302 ms

logo-gdb.svg

logo-gdb.svg

175 ms

spinner.gif

spinner.gif

180 ms

search.svg

search.svg

268 ms

social-linkedin.svg

social-linkedin.svg

268 ms

social-instagram.svg

social-instagram.svg

296 ms

iStock-1338846836-scaled.jpg

iStock-1338846836-scaled.jpg

482 ms

grafismo2.svg

grafismo2.svg

355 ms

grafismo1.svg

grafismo1.svg

356 ms

img-ctv.png

img-ctv.png

654 ms

img-carbon-free.png

img-carbon-free.png

600 ms

img-video.png

img-video.png

599 ms

img-audio.png

img-audio.png

664 ms

img-display.png

img-display.png

609 ms

img-native.png

img-native.png

605 ms

grafismo3.svg

grafismo3.svg

661 ms

triangle.svg

triangle.svg

662 ms

triangle-pink.svg

triangle-pink.svg

669 ms

triangle-left.svg

triangle-left.svg

671 ms

7Auup_AqnyWWAxW2Wk3swUz56MS91Eww8Rf21nmjpw.ttf

7Auup_AqnyWWAxW2Wk3swUz56MS91Eww8Rf21nmjpw.ttf

23 ms

7Auup_AqnyWWAxW2Wk3swUz56MS91Eww8SX21nmjpw.ttf

7Auup_AqnyWWAxW2Wk3swUz56MS91Eww8SX21nmjpw.ttf

28 ms

7Auup_AqnyWWAxW2Wk3swUz56MS91Eww8fvx1nmjpw.ttf

7Auup_AqnyWWAxW2Wk3swUz56MS91Eww8fvx1nmjpw.ttf

39 ms

7Auup_AqnyWWAxW2Wk3swUz56MS91Eww8cLx1nmjpw.ttf

7Auup_AqnyWWAxW2Wk3swUz56MS91Eww8cLx1nmjpw.ttf

39 ms

7Auup_AqnyWWAxW2Wk3swUz56MS91Eww8aXx1nmjpw.ttf

7Auup_AqnyWWAxW2Wk3swUz56MS91Eww8aXx1nmjpw.ttf

264 ms

7Auup_AqnyWWAxW2Wk3swUz56MS91Eww8Yzx1nmjpw.ttf

7Auup_AqnyWWAxW2Wk3swUz56MS91Eww8Yzx1nmjpw.ttf

147 ms

object2.svg

object2.svg

714 ms

logo-gdb-white.svg

logo-gdb-white.svg

710 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4uaVc.ttf

13 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf

3 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf

6 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf

13 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf

14 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVc.ttf

14 ms

arrow-left.svg

arrow-left.svg

334 ms

arrow-right.svg

arrow-right.svg

335 ms

modules.woff

modules.woff

338 ms

cmp.php

cmp.php

388 ms

cmp.php

cmp.php

400 ms

bV8xLndfNjE0ODMucl9HRFBSLmxfZW4uZF8yMjcyNy54XzEyLnYucC50XzIyNzI3Lnh0XzU.js

bV8xLndfNjE0ODMucl9HRFBSLmxfZW4uZF8yMjcyNy54XzEyLnYucC50XzIyNzI3Lnh0XzU.js

777 ms

Accessibility Review

gdb.net accessibility score

89

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

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

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

gdb.net best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

gdb.net SEO score

90

Search Engine Optimization Advices

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    PT

  • Language Claimed

    PT

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Gdb.net 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 Gdb.net 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.

Social Sharing Optimization

gdb.net

Open Graph description is not detected on the main page of GDB. 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: