5.8 sec in total
138 ms
3.2 sec
2.5 sec
Visit guardianz.io now to see the best up-to-date Guardianz content and also check out these interesting facts you probably never knew about guardianz.io
DiemLibre NFT marketplace. Create, Buy, Bell, and Auction NFTs and Cryto Collectibles powered by $DLB. Become the next NFT Millionaire by earning Creator Royalties forever.
Visit guardianz.ioWe analyzed Guardianz.io page load time and found that the first response time was 138 ms and then it took 5.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
guardianz.io performance score
name
value
score
weighting
Value8.1 s
0/100
10%
Value9.0 s
1/100
25%
Value9.3 s
13/100
10%
Value1,350 ms
17/100
30%
Value0.018
100/100
15%
Value9.5 s
30/100
10%
138 ms
640 ms
104 ms
105 ms
101 ms
Our browser made a total of 46 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Guardianz.io, 57% (26 requests) were made to Nft.diemlibre.org and 24% (11 requests) were made to Unpkg.com. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Nft.diemlibre.org.
Page size can be reduced by 162.4 kB (42%)
384.2 kB
221.8 kB
In fact, the total size of Guardianz.io main page is 384.2 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 176.5 kB which makes up the majority of the site volume.
Potential reduce by 104.3 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 35.2 kB, which is 29% 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 104.3 kB or 85% of the original size.
Potential reduce by 6.3 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. Guardianz images are well optimized though.
Potential reduce by 33.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 33.3 kB or 58% of the original size.
Potential reduce by 18.5 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. Guardianz.io needs all CSS files to be minified and compressed as it can save up to 18.5 kB or 70% of the original size.
Number of requests can be reduced by 22 (67%)
33
11
The browser has sent 33 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Guardianz. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
guardianz.io
138 ms
nft.diemlibre.org
640 ms
css2
104 ms
swiper-bundle.min.css
105 ms
toastify.min.css
101 ms
font-awesome.min.css
141 ms
style.css
339 ms
css.css
284 ms
darkMode.bundle.js
285 ms
my.bundle.js
1306 ms
moment.min.js
93 ms
toastify-js
87 ms
swiper-bundle.min.js
86 ms
sweetalert.min.js
92 ms
dayjs.min.js
93 ms
core@2
90 ms
tippy.js@6
91 ms
jquery.initialize.min.js
346 ms
value_equals.js
346 ms
filesize.min.js
368 ms
detect-provider.min.js
367 ms
config.js
431 ms
js
119 ms
app.bundle.js
656 ms
script.js
551 ms
index.js
467 ms
core@2.11.6
34 ms
tippy.js@6.3.7
28 ms
sweetalert.min.js
32 ms
tippy-bundle.umd.min.js
17 ms
popper.min.js
12 ms
26a1.png
102 ms
logo.png
322 ms
logo_white.png
220 ms
gradient.jpg
136 ms
gradient_dark.jpg
208 ms
3D_elements.png
208 ms
gradient_light.jpg
115 ms
owner.jpg
206 ms
analytics.js
52 ms
4ee96395e07a04577aab.ttf
481 ms
150680530af9dd9fd00b.ttf
373 ms
c423ce2dc1d85bc50799.ttf
246 ms
b8c456ff9fd96840cdca.woff
443 ms
fontawesome-webfont.woff
590 ms
collect
15 ms
guardianz.io 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.
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
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.
guardianz.io 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
Missing source maps for large first-party JavaScript
guardianz.io SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
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 Guardianz.io 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 Guardianz.io 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.
guardianz.io
Open Graph data is detected on the main page of Guardianz. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: