7.8 sec in total
1.3 sec
6.1 sec
418 ms
Click here to check amazing GBIF content for Mexico. Otherwise, check out these important facts you probably never knew about gbif.org
Visit gbif.orgWe analyzed Gbif.org page load time and found that the first response time was 1.3 sec and then it took 6.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
gbif.org performance score
name
value
score
weighting
Value3.6 s
34/100
10%
Value4.3 s
41/100
25%
Value9.6 s
12/100
10%
Value1,440 ms
15/100
30%
Value0.001
100/100
15%
Value14.9 s
8/100
10%
1254 ms
2335 ms
190 ms
195 ms
196 ms
Our browser made a total of 54 requests to load all elements on the main page. We found that 69% of them (37 requests) were addressed to the original Gbif.org, 7% (4 requests) were made to Api.gbif.org and 4% (2 requests) were made to Platform.linkedin.com. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Gbif.org.
Page size can be reduced by 703.0 kB (56%)
1.3 MB
550.3 kB
In fact, the total size of Gbif.org main page is 1.3 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. 60% of websites need less resources to load. Javascripts take 638.5 kB which makes up the majority of the site volume.
Potential reduce by 34.2 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 34.2 kB or 76% of the original size.
Potential reduce by 41.0 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. Obviously, GBIF needs image optimization as it can save up to 41.0 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 455.5 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 455.5 kB or 71% of the original size.
Potential reduce by 172.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. Gbif.org needs all CSS files to be minified and compressed as it can save up to 172.2 kB or 82% of the original size.
Number of requests can be reduced by 21 (41%)
51
30
The browser has sent 51 CSS, Javascripts, AJAX and image requests in order to completely render the main page of GBIF. 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 5 to 1 for CSS and as a result speed up the page load time.
gbif.org
1254 ms
www.gbif.org
2335 ms
css_lQaZfjVpwP_oGNqdtWCSpJT1EMqXdMiU84ekLLxQnc4.css
190 ms
css_tGTNtRAsNJmcVz4r7F6YCijbrQGDbBmziHSrRd1Stqc.css
195 ms
css_xzic57KdepQa86psLfqxiSDZSjZqFrBpUV1whsbfucc.css
196 ms
css_ORkYAsOOU_S5cdFsPKueDfxmQ6foykAi-45FbiK4OLc.css
197 ms
css_DUzxL6DqWC4G6sbIZCWpvtXxa63ZbhgKrLKPCY47Mok.css
294 ms
js_JLxuxbhhrFRy-sBnijHkR0TGGHgiukMPv94zvDWgQ3g.js
330 ms
js_dAlLv5DYHo-gFdfnMj1Orh1I9bRC06ArVqF4JTDO3Ck.js
285 ms
js_T7-uqLHBCNzA3NC-DSROkGJ9hxEbpY-jYTqm6p4hJYY.js
292 ms
in.js
7 ms
js_aXysGQtVhODZEGYQkI_7b1TtT2ymH_Fiidh3yK3fk-I.js
288 ms
js_3esK3-rqUKZM0U66mnH4pPYJZ9OFZ12X8prc6LMjb28.js
494 ms
js_xlW8X6dm5McwxzszwuhO35Mt0XYvRral0HkM7YN0Djw.js
311 ms
js__6iN6iPsQJtiaS0h13UgDN04MgqbIuNH_WumBizNOmo.js
312 ms
analytics.js
39 ms
logo_white.png
100 ms
input_bkg.png
101 ms
button_search.png
98 ms
musk-ox-bull-animal-ovibos-moschatus.jpg
104 ms
calendar.png
107 ms
devastazyon-Malpolon-monspessulanus-web.jpg
195 ms
SI-wild-Ursus_thibetanus.jpg
197 ms
garcia-rosello-map.jpg
195 ms
footer_bkg.jpg
1626 ms
images.png
1626 ms
social-icons.png
1627 ms
collect
14 ms
collect
59 ms
secureAnonymousFramework
1396 ms
plusone.js
1437 ms
all.js
1407 ms
widgets.js
1365 ms
count
237 ms
metrics
239 ms
search
237 ms
count
258 ms
a2e9eca4
600 ms
2.png
205 ms
2.png
133 ms
1.png
221 ms
1.png
249 ms
3.png
224 ms
3.png
173 ms
2.png
231 ms
2.png
348 ms
1.png
300 ms
1.png
317 ms
3.png
320 ms
3.png
327 ms
153 ms
xd_arbiter.php
84 ms
xd_arbiter.php
139 ms
cb=gapi.loaded_0
33 ms
gbif.org 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
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
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
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.
gbif.org 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
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
gbif.org SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Gbif.org can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Gbif.org 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.
gbif.org
Open Graph description is not detected on the main page of GBIF. 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: