Tools & Wizards About Us
discoveringtreasures.org screenshot

Report Summary

  • 27

    Performance

    Renders faster than
    47% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 89% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

discoveringtreasures.org

Discovering Treasures - Annual Word Conference of The Carpenter's Church, Greenville, Port Harcourt, Nigeria

Page Load Speed

15.3 sec in total

First Response

142 ms

Resources Loaded

14.6 sec

Page Rendered

554 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

Discovering Treasures is an annual Word Conference that holds every February at Greenville, in the beautiful city of Port Harcourt, Nigeria. It helps to prepare delegates for the rest of the year with...

Visit discoveringtreasures.org

Key Findings

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

Performance Metrics

discoveringtreasures.org performance score

27

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

32/100

10%

LCP (Largest Contentful Paint)

Value5.2 s

23/100

25%

SI (Speed Index)

Value15.2 s

1/100

10%

TBT (Total Blocking Time)

Value1,300 ms

18/100

30%

CLS (Cumulative Layout Shift)

Value0.123

84/100

15%

TTI (Time to Interactive)

Value34.8 s

0/100

10%

Network Requests Diagram

discoveringtreasures.org

142 ms

discoveringtreasures.org

500 ms

main.min.css

207 ms

css

29 ms

sbi-styles.min.css

211 ms

Our browser made a total of 132 requests to load all elements on the main page. We found that 88% of them (116 requests) were addressed to the original Discoveringtreasures.org, 8% (11 requests) were made to Fonts.gstatic.com and 2% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (12.4 sec) belongs to the original domain Discoveringtreasures.org.

Page Optimization Overview & Recommendations

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

Content Size

9.7 MB

After Optimization

8.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Discoveringtreasures.org main page is 9.7 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

-82%

Potential reduce by 179.8 kB

  • Original 218.5 kB
  • After minification 215.2 kB
  • After compression 38.7 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 179.8 kB or 82% 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

-12%

Potential reduce by 100.1 kB

  • Original 807.3 kB
  • After minification 807.3 kB
  • After compression 707.2 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 100.1 kB or 12% of the original size.

CSS Optimization

-23%

Potential reduce by 50.2 kB

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

Requests Breakdown

Number of requests can be reduced by 103 (89%)

Requests Now

116

After Optimization

13

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 116 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 73 to 1 for JavaScripts and from 32 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

discoveringtreasures.org

discoveringtreasures.org

142 ms

discoveringtreasures.org

discoveringtreasures.org

500 ms

main.min.css

main.min.css

207 ms

css

css

29 ms

sbi-styles.min.css

sbi-styles.min.css

211 ms

styles.css

styles.css

153 ms

contact-form-7-main.min.css

contact-form-7-main.min.css

210 ms

woocommerce-layout-grid.min.css

woocommerce-layout-grid.min.css

218 ms

woocommerce-grid.min.css

woocommerce-grid.min.css

296 ms

header-footer-elementor.css

header-footer-elementor.css

221 ms

frontend.min.css

frontend.min.css

309 ms

general.min.css

general.min.css

234 ms

eael-4.css

eael-4.css

292 ms

elementor-icons.min.css

elementor-icons.min.css

302 ms

swiper.min.css

swiper.min.css

304 ms

post-442.css

post-442.css

322 ms

frontend.min.css

frontend.min.css

582 ms

all.min.css

all.min.css

442 ms

v4-shims.min.css

v4-shims.min.css

381 ms

post-4.css

post-4.css

379 ms

frontend.css

frontend.css

392 ms

css

css

16 ms

fontawesome.min.css

fontawesome.min.css

466 ms

brands.min.css

brands.min.css

452 ms

regular.min.css

regular.min.css

453 ms

solid.min.css

solid.min.css

465 ms

smartslider.min.css

smartslider.min.css

523 ms

jquery.min.js

jquery.min.js

601 ms

jquery-migrate.min.js

jquery-migrate.min.js

530 ms

jquery.blockUI.min.js

jquery.blockUI.min.js

544 ms

add-to-cart.min.js

add-to-cart.min.js

543 ms

js.cookie.min.js

js.cookie.min.js

613 ms

woocommerce.min.js

woocommerce.min.js

615 ms

v4-shims.min.js

v4-shims.min.js

620 ms

n2.min.js

n2.min.js

638 ms

smartslider-frontend.min.js

smartslider-frontend.min.js

762 ms

ss-simple.min.js

ss-simple.min.js

709 ms

css

css

13 ms

font-awesome.css

font-awesome.css

652 ms

wc-blocks.css

wc-blocks.css

651 ms

rs6.css

rs6.css

663 ms

photoswipe.min.css

photoswipe.min.css

586 ms

default-skin.min.css

default-skin.min.css

643 ms

frontend.min.js

frontend.min.js

677 ms

index.js

index.js

621 ms

index.js

index.js

613 ms

rbtools.min.js

rbtools.min.js

779 ms

rs6.min.js

rs6.min.js

816 ms

sourcebuster.min.js

sourcebuster.min.js

575 ms

order-attribution.min.js

order-attribution.min.js

579 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

574 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

578 ms

wp-polyfill.min.js

wp-polyfill.min.js

709 ms

react.min.js

react.min.js

634 ms

hooks.min.js

hooks.min.js

572 ms

deprecated.min.js

deprecated.min.js

573 ms

dom.min.js

dom.min.js

646 ms

react-dom.min.js

react-dom.min.js

735 ms

escape-html.min.js

escape-html.min.js

589 ms

element.min.js

element.min.js

619 ms

is-shallow-equal.min.js

is-shallow-equal.min.js

619 ms

i18n.min.js

i18n.min.js

633 ms

keycodes.min.js

keycodes.min.js

580 ms

priority-queue.min.js

priority-queue.min.js

590 ms

compose.min.js

compose.min.js

602 ms

private-apis.min.js

private-apis.min.js

611 ms

redux-routine.min.js

redux-routine.min.js

591 ms

data.min.js

data.min.js

579 ms

lodash.min.js

lodash.min.js

583 ms

wc-blocks-registry.js

wc-blocks-registry.js

604 ms

url.min.js

url.min.js

590 ms

o-0mIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjcz6L1SoM-jCpoiyD9A-9a6VQ.woff

o-0mIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjcz6L1SoM-jCpoiyD9A-9a6VQ.woff

88 ms

o-0mIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjcz6L1SoM-jCpoiyAaBO9a6VQ.woff

o-0mIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjcz6L1SoM-jCpoiyAaBO9a6VQ.woff

97 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aXw.woff

105 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aXw.woff

112 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aXw.woff

112 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw5aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw5aXw.woff

113 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw5aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw5aXw.woff

115 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aXw.woff

115 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aXw.woff

112 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w5aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w5aXw.woff

113 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w5aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w5aXw.woff

115 ms

api-fetch.min.js

api-fetch.min.js

618 ms

wc-settings.js

wc-settings.js

552 ms

data-controls.min.js

data-controls.min.js

548 ms

html-entities.min.js

html-entities.min.js

551 ms

notices.min.js

notices.min.js

568 ms

wc-blocks-middleware.js

wc-blocks-middleware.js

574 ms

embed

embed

374 ms

wc-blocks-data.js

wc-blocks-data.js

643 ms

dom-ready.min.js

dom-ready.min.js

509 ms

a11y.min.js

a11y.min.js

513 ms

primitives.min.js

primitives.min.js

521 ms

warning.min.js

warning.min.js

541 ms

blocks-components.js

blocks-components.js

579 ms

blocks-checkout.js

blocks-checkout.js

603 ms

order-attribution-blocks.min.js

order-attribution-blocks.min.js

543 ms

main.js

main.js

544 ms

general.min.js

general.min.js

491 ms

eael-4.js

eael-4.js

537 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

546 ms

webpack.runtime.min.js

webpack.runtime.min.js

483 ms

frontend-modules.min.js

frontend-modules.min.js

480 ms

frontend.min.js

frontend.min.js

481 ms

waypoints.min.js

waypoints.min.js

514 ms

core.min.js

core.min.js

509 ms

frontend.min.js

frontend.min.js

584 ms

elements-handlers.min.js

elements-handlers.min.js

498 ms

underscore.min.js

underscore.min.js

537 ms

wp-util.min.js

wp-util.min.js

534 ms

frontend.min.js

frontend.min.js

520 ms

js

js

58 ms

jquery.zoom.min.js

jquery.zoom.min.js

497 ms

jquery.flexslider.min.js

jquery.flexslider.min.js

519 ms

photoswipe.min.js

photoswipe.min.js

530 ms

photoswipe-ui-default.min.js

photoswipe-ui-default.min.js

530 ms

add-to-cart-variation.min.js

add-to-cart-variation.min.js

530 ms

single-product.min.js

single-product.min.js

534 ms

fa-brands-400.woff

fa-brands-400.woff

793 ms

fa-regular-400.woff

fa-regular-400.woff

505 ms

fa-solid-900.woff

fa-solid-900.woff

668 ms

sbi-sprite.png

sbi-sprite.png

532 ms

cropped-DT2024-logo-120x120.png

cropped-DT2024-logo-120x120.png

545 ms

dummy.png

dummy.png

537 ms

DT-2024-UPDATED-BANNER.png

DT-2024-UPDATED-BANNER.png

2137 ms

DT2024-PK-734x1024.png

DT2024-PK-734x1024.png

1373 ms

DT2024-TA-734x1024.png

DT2024-TA-734x1024.png

1372 ms

DT2024-PL-734x1024.png

DT2024-PL-734x1024.png

1155 ms

DT2024-NO-734x1024.png

DT2024-NO-734x1024.png

1398 ms

confrico-Maiores02.jpg

confrico-Maiores02.jpg

722 ms

admin-ajax.php

admin-ajax.php

12442 ms

woocommerce-smallscreen-grid.min.css

woocommerce-smallscreen-grid.min.css

73 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: