Tools & Wizards About Us
discoveringtreasures.org screenshot

Report Summary

  • 22

    Performance

    Renders faster than
    40% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 88% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

discoveringtreasures.org

DT2024 – Discovering Treasures

Page Load Speed

2.9 sec in total

First Response

168 ms

Resources Loaded

2.3 sec

Page Rendered

443 ms

discoveringtreasures.org screenshot

About Website

Welcome to discoveringtreasures.org homepage info - get ready to check Discovering Treasures best content for Nigeria right away, or after learning these important things about discoveringtreasures.org

Visit discoveringtreasures.org

Key Findings

We analyzed Discoveringtreasures.org page load time and found that the first response time was 168 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

discoveringtreasures.org performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.8 s

12/100

10%

LCP (Largest Contentful Paint)

Value6.2 s

11/100

25%

SI (Speed Index)

Value18.9 s

0/100

10%

TBT (Total Blocking Time)

Value1,250 ms

19/100

30%

CLS (Cumulative Layout Shift)

Value0.131

81/100

15%

TTI (Time to Interactive)

Value34.8 s

0/100

10%

Network Requests Diagram

discoveringtreasures.org

168 ms

discoveringtreasures.org

372 ms

main.min.css

131 ms

css

32 ms

sbi-styles.min.css

189 ms

Our browser made a total of 111 requests to load all elements on the main page. We found that 83% of them (92 requests) were addressed to the original Discoveringtreasures.org, 10% (11 requests) were made to Fonts.gstatic.com and 4% (4 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (857 ms) belongs to the original domain Discoveringtreasures.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 938.9 kB (10%)

Content Size

9.5 MB

After Optimization

8.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Discoveringtreasures.org main page is 9.5 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. 65% of websites need less resources to load. Images take 8.5 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 173.2 kB

  • Original 208.4 kB
  • After minification 205.0 kB
  • After compression 35.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 173.2 kB or 83% of the original size.

Image Optimization

-8%

Potential reduce by 642.3 kB

  • Original 8.5 MB
  • After minification 7.8 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. Discovering Treasures images are well optimized though.

JavaScript Optimization

-13%

Potential reduce by 74.8 kB

  • Original 590.1 kB
  • After minification 590.1 kB
  • After compression 515.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 74.8 kB or 13% of the original size.

CSS Optimization

-22%

Potential reduce by 48.5 kB

  • Original 219.1 kB
  • After minification 219.1 kB
  • After compression 170.6 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. Discoveringtreasures.org needs all CSS files to be minified and compressed as it can save up to 48.5 kB or 22% of the original size.

Requests Breakdown

Number of requests can be reduced by 82 (86%)

Requests Now

95

After Optimization

13

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

discoveringtreasures.org

discoveringtreasures.org

168 ms

discoveringtreasures.org

discoveringtreasures.org

372 ms

main.min.css

main.min.css

131 ms

css

css

32 ms

sbi-styles.min.css

sbi-styles.min.css

189 ms

frontend.css

frontend.css

203 ms

styles.css

styles.css

215 ms

contact-form-7-main.min.css

contact-form-7-main.min.css

216 ms

woocommerce-layout-grid.min.css

woocommerce-layout-grid.min.css

206 ms

woocommerce-grid.min.css

woocommerce-grid.min.css

217 ms

header-footer-elementor.css

header-footer-elementor.css

251 ms

frontend.min.css

frontend.min.css

283 ms

general.min.css

general.min.css

286 ms

eael-4.css

eael-4.css

286 ms

elementor-icons.min.css

elementor-icons.min.css

288 ms

swiper.min.css

swiper.min.css

287 ms

e-swiper.min.css

e-swiper.min.css

325 ms

post-442.css

post-442.css

349 ms

frontend.min.css

frontend.min.css

479 ms

all.min.css

all.min.css

422 ms

v4-shims.min.css

v4-shims.min.css

360 ms

post-4.css

post-4.css

366 ms

css

css

27 ms

fontawesome.min.css

fontawesome.min.css

389 ms

brands.min.css

brands.min.css

411 ms

regular.min.css

regular.min.css

424 ms

solid.min.css

solid.min.css

437 ms

smartslider.min.css

smartslider.min.css

461 ms

jquery.min.js

jquery.min.js

537 ms

jquery-migrate.min.js

jquery-migrate.min.js

494 ms

jquery.blockUI.min.js

jquery.blockUI.min.js

494 ms

add-to-cart.min.js

add-to-cart.min.js

500 ms

js.cookie.min.js

js.cookie.min.js

529 ms

woocommerce.min.js

woocommerce.min.js

546 ms

v4-shims.min.js

v4-shims.min.js

562 ms

n2.min.js

n2.min.js

583 ms

smartslider-frontend.min.js

smartslider-frontend.min.js

687 ms

ss-simple.min.js

ss-simple.min.js

685 ms

css

css

28 ms

font-awesome.css

font-awesome.css

684 ms

wc-blocks.css

wc-blocks.css

640 ms

widget-heading.min.css

widget-heading.min.css

565 ms

widget-text-editor.min.css

widget-text-editor.min.css

504 ms

widget-divider.min.css

widget-divider.min.css

558 ms

widget-image.min.css

widget-image.min.css

556 ms

widget-image-box.min.css

widget-image-box.min.css

546 ms

widget-social-icons.min.css

widget-social-icons.min.css

552 ms

apple-webkit.min.css

apple-webkit.min.css

544 ms

widget-icon-box.min.css

widget-icon-box.min.css

510 ms

widget-google_maps.min.css

widget-google_maps.min.css

543 ms

rs6.css

rs6.css

538 ms

photoswipe.min.css

photoswipe.min.css

540 ms

default-skin.min.css

default-skin.min.css

544 ms

frontend.min.js

frontend.min.js

563 ms

hooks.min.js

hooks.min.js

534 ms

i18n.min.js

i18n.min.js

538 ms

index.js

index.js

549 ms

index.js

index.js

540 ms

rbtools.min.js

rbtools.min.js

577 ms

rs6.min.js

rs6.min.js

672 ms

dom-ready.min.js

dom-ready.min.js

507 ms

main.js

main.js

526 ms

general.min.js

general.min.js

550 ms

eael-4.js

eael-4.js

523 ms

sourcebuster.min.js

sourcebuster.min.js

507 ms

order-attribution.min.js

order-attribution.min.js

526 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

554 ms

webpack.runtime.min.js

webpack.runtime.min.js

551 ms

frontend-modules.min.js

frontend-modules.min.js

533 ms

frontend.min.js

frontend.min.js

520 ms

core.min.js

core.min.js

545 ms

frontend.min.js

frontend.min.js

530 ms

o-0mIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjcz6L1SoM-jCpoiyD9A-9a6Vc.ttf

o-0mIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjcz6L1SoM-jCpoiyD9A-9a6Vc.ttf

105 ms

o-0mIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjcz6L1SoM-jCpoiyAaBO9a6Vc.ttf

o-0mIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjcz6L1SoM-jCpoiyAaBO9a6Vc.ttf

137 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

154 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf

148 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf

156 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw5aX8.ttf

165 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw5aX8.ttf

157 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf

164 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf

156 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w5aX8.ttf

157 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w5aX8.ttf

165 ms

preloaded-elements-handlers.min.js

preloaded-elements-handlers.min.js

599 ms

jquery.zoom.min.js

jquery.zoom.min.js

469 ms

jquery.flexslider.min.js

jquery.flexslider.min.js

484 ms

photoswipe.min.js

photoswipe.min.js

491 ms

photoswipe-ui-default.min.js

photoswipe-ui-default.min.js

496 ms

underscore.min.js

underscore.min.js

504 ms

wp-util.min.js

wp-util.min.js

534 ms

embed

embed

726 ms

add-to-cart-variation.min.js

add-to-cart-variation.min.js

481 ms

single-product.min.js

single-product.min.js

487 ms

fa-brands-400.woff

fa-brands-400.woff

550 ms

fa-regular-400.woff

fa-regular-400.woff

494 ms

fa-solid-900.woff

fa-solid-900.woff

567 ms

sbi-sprite.png

sbi-sprite.png

525 ms

cropped-DT2024-logo-120x120.png

cropped-DT2024-logo-120x120.png

485 ms

dummy.png

dummy.png

483 ms

DT-2024-UPDATED-BANNER.png

DT-2024-UPDATED-BANNER.png

857 ms

DT2024-PK-734x1024.png

DT2024-PK-734x1024.png

830 ms

DT2024-TA-734x1024.png

DT2024-TA-734x1024.png

794 ms

DT2024-PL-734x1024.png

DT2024-PL-734x1024.png

848 ms

DT2024-NO-734x1024.png

DT2024-NO-734x1024.png

703 ms

confrico-Maiores02.jpg

confrico-Maiores02.jpg

505 ms

default-skin.png

default-skin.png

579 ms

js

js

26 ms

search.js

search.js

3 ms

geometry.js

geometry.js

6 ms

main.js

main.js

10 ms

woocommerce-smallscreen-grid.min.css

woocommerce-smallscreen-grid.min.css

72 ms

Accessibility Review

discoveringtreasures.org accessibility score

96

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

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

High

Links do not have a discernible name

Best Practices

discoveringtreasures.org best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

discoveringtreasures.org SEO score

79

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

Social Sharing Optimization

discoveringtreasures.org

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