Tools & Wizards About Us
crystalforum.co.za screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

crystalforum.co.za

Crystal Forum | Preciosa Crystals & Crystalp Jewelery

Page Load Speed

13.3 sec in total

First Response

758 ms

Resources Loaded

12.2 sec

Page Rendered

274 ms

crystalforum.co.za screenshot

About Website

Welcome to crystalforum.co.za homepage info - get ready to check Crystal Forum best content for South Africa right away, or after learning these important things about crystalforum.co.za

Visit our Crystalp Jewellery Shop find out about Crystalp Jewellery Wholesale Find out about textile & jewellery crystal components about innovations Read more about Crystal Forum CRYSTAL FORUM has be...

Visit crystalforum.co.za

Key Findings

We analyzed Crystalforum.co.za page load time and found that the first response time was 758 ms and then it took 12.5 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

crystalforum.co.za performance score

0

Network Requests Diagram

crystalforum.co.za

758 ms

www.crystalforum.co.za

1373 ms

shortcodes.css

749 ms

styles.css

744 ms

cookie-law-info-public.css

774 ms

Our browser made a total of 139 requests to load all elements on the main page. We found that 90% of them (125 requests) were addressed to the original Crystalforum.co.za, 6% (9 requests) were made to Fonts.gstatic.com and 1% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.8 sec) belongs to the original domain Crystalforum.co.za.

Page Optimization Overview & Recommendations

Page size can be reduced by 3.2 MB (65%)

Content Size

5.0 MB

After Optimization

1.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Crystalforum.co.za main page is 5.0 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. Javascripts take 2.4 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 110.7 kB

  • Original 138.1 kB
  • After minification 130.5 kB
  • After compression 27.4 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 110.7 kB or 80% of the original size.

Image Optimization

-0%

Potential reduce by 2.7 kB

  • Original 592.3 kB
  • After minification 589.6 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. Crystal Forum images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 1.5 MB

  • Original 2.4 MB
  • After minification 2.4 MB
  • After compression 857.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 1.5 MB or 64% of the original size.

CSS Optimization

-87%

Potential reduce by 1.6 MB

  • Original 1.8 MB
  • After minification 1.7 MB
  • After compression 241.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. Crystalforum.co.za needs all CSS files to be minified and compressed as it can save up to 1.6 MB or 87% of the original size.

Requests Breakdown

Number of requests can be reduced by 112 (90%)

Requests Now

125

After Optimization

13

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

crystalforum.co.za

crystalforum.co.za

758 ms

www.crystalforum.co.za

www.crystalforum.co.za

1373 ms

shortcodes.css

shortcodes.css

749 ms

styles.css

styles.css

744 ms

cookie-law-info-public.css

cookie-law-info-public.css

774 ms

cookie-law-info-gdpr.css

cookie-law-info-gdpr.css

1029 ms

all.min.css

all.min.css

1528 ms

bootstrap.min.css

bootstrap.min.css

1295 ms

front.css

front.css

1486 ms

woocommerce-layout.css

woocommerce-layout.css

1249 ms

woocommerce.css

woocommerce.css

1270 ms

wp-ulike.min.css

wp-ulike.min.css

1308 ms

base.css

base.css

2229 ms

auxin-icon.css

auxin-icon.css

1522 ms

main.css

main.css

2578 ms

css

css

32 ms

custom.css

custom.css

1565 ms

frontend.min.css

frontend.min.css

1991 ms

post-5175.css

post-5175.css

1777 ms

post-5795.css

post-5795.css

1786 ms

elementor-icons.min.css

elementor-icons.min.css

1842 ms

swiper.min.css

swiper.min.css

2040 ms

e-swiper.min.css

e-swiper.min.css

2049 ms

post-5595.css

post-5595.css

2100 ms

elementor.css

elementor.css

2252 ms

elementor-widgets.css

elementor-widgets.css

2300 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

2335 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

2358 ms

all.min.css

all.min.css

2488 ms

v4-shims.min.css

v4-shims.min.css

2506 ms

post-5208.css

post-5208.css

2552 ms

css

css

33 ms

fontawesome.min.css

fontawesome.min.css

2842 ms

brands.min.css

brands.min.css

2614 ms

jquery.min.js

jquery.min.js

2751 ms

jquery-migrate.min.js

jquery-migrate.min.js

2759 ms

cookie-law-info-public.js

cookie-law-info-public.js

2810 ms

popper.min.js

popper.min.js

2840 ms

js

js

61 ms

api.js

api.js

41 ms

wc-blocks.css

wc-blocks.css

2645 ms

widget-social-icons.min.css

widget-social-icons.min.css

2507 ms

apple-webkit.min.css

apple-webkit.min.css

2279 ms

widget-spacer.min.css

widget-spacer.min.css

2320 ms

widget-text-editor.min.css

widget-text-editor.min.css

2336 ms

cookie-law-info-table.css

cookie-law-info-table.css

2076 ms

bootstrap.min.js

bootstrap.min.js

2144 ms

front.js

front.js

1991 ms

jquery.blockUI.min.js

jquery.blockUI.min.js

1990 ms

add-to-cart.min.js

add-to-cart.min.js

2015 ms

js.cookie.min.js

js.cookie.min.js

1882 ms

woocommerce.min.js

woocommerce.min.js

1849 ms

modernizr-custom.min.js

modernizr-custom.min.js

1993 ms

v4-shims.min.js

v4-shims.min.js

2019 ms

imagesloaded.min.js

imagesloaded.min.js

1833 ms

masonry.min.js

masonry.min.js

1874 ms

plugins.min.js

plugins.min.js

1818 ms

scripts.min.js

scripts.min.js

1668 ms

widgets.js

widgets.js

1760 ms

mediaelement-and-player.min.js

mediaelement-and-player.min.js

1989 ms

mediaelement-migrate.min.js

mediaelement-migrate.min.js

1726 ms

wp-mediaelement.min.js

wp-mediaelement.min.js

1655 ms

plugins.min.js

plugins.min.js

1667 ms

scripts.js

scripts.js

1619 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

1719 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

1717 ms

wp-polyfill.min.js

wp-polyfill.min.js

1907 ms

hooks.min.js

hooks.min.js

1677 ms

i18n.min.js

i18n.min.js

1632 ms

index.js

index.js

1687 ms

index.js

index.js

1683 ms

jquery.form.min.js

jquery.form.min.js

1575 ms

sourcebuster.min.js

sourcebuster.min.js

1688 ms

order-attribution.min.js

order-attribution.min.js

1637 ms

react.min.js

react.min.js

1704 ms

deprecated.min.js

deprecated.min.js

1681 ms

dom.min.js

dom.min.js

1696 ms

react-dom.min.js

react-dom.min.js

1658 ms

escape-html.min.js

escape-html.min.js

1689 ms

element.min.js

element.min.js

1653 ms

is-shallow-equal.min.js

is-shallow-equal.min.js

1696 ms

keycodes.min.js

keycodes.min.js

1691 ms

priority-queue.min.js

priority-queue.min.js

1568 ms

compose.min.js

compose.min.js

1641 ms

private-apis.min.js

private-apis.min.js

1646 ms

redux-routine.min.js

redux-routine.min.js

1612 ms

data.min.js

data.min.js

1678 ms

lodash.min.js

lodash.min.js

1659 ms

wc-blocks-registry.js

wc-blocks-registry.js

1504 ms

url.min.js

url.min.js

1578 ms

api-fetch.min.js

api-fetch.min.js

1568 ms

wc-settings.js

wc-settings.js

1584 ms

data-controls.min.js

data-controls.min.js

1641 ms

pxiEyp8kv8JHgFVrJJfedw.ttf

pxiEyp8kv8JHgFVrJJfedw.ttf

36 ms

pxiByp8kv8JHgFVrLGT9Z1xlEA.ttf

pxiByp8kv8JHgFVrLGT9Z1xlEA.ttf

86 ms

pxiByp8kv8JHgFVrLDz8Z1xlEA.ttf

pxiByp8kv8JHgFVrLDz8Z1xlEA.ttf

109 ms

pxiByp8kv8JHgFVrLFj_Z1xlEA.ttf

pxiByp8kv8JHgFVrLFj_Z1xlEA.ttf

116 ms

pxiGyp8kv8JHgFVrLPTucHtF.ttf

pxiGyp8kv8JHgFVrLPTucHtF.ttf

118 ms

pxiByp8kv8JHgFVrLEj6Z1xlEA.ttf

pxiByp8kv8JHgFVrLEj6Z1xlEA.ttf

117 ms

pxiByp8kv8JHgFVrLCz7Z1xlEA.ttf

pxiByp8kv8JHgFVrLCz7Z1xlEA.ttf

117 ms

pxiByp8kv8JHgFVrLDD4Z1xlEA.ttf

pxiByp8kv8JHgFVrLDD4Z1xlEA.ttf

116 ms

pxiByp8kv8JHgFVrLBT5Z1xlEA.ttf

pxiByp8kv8JHgFVrLBT5Z1xlEA.ttf

117 ms

html-entities.min.js

html-entities.min.js

1645 ms

notices.min.js

notices.min.js

1537 ms

wc-blocks-middleware.js

wc-blocks-middleware.js

1621 ms

wc-blocks-data.js

wc-blocks-data.js

1601 ms

dom-ready.min.js

dom-ready.min.js

1588 ms

a11y.min.js

a11y.min.js

1634 ms

primitives.min.js

primitives.min.js

1503 ms

warning.min.js

warning.min.js

1536 ms

blocks-components.js

blocks-components.js

1641 ms

blocks-checkout.js

blocks-checkout.js

1568 ms

order-attribution-blocks.min.js

order-attribution-blocks.min.js

1584 ms

wp-ulike.min.js

wp-ulike.min.js

1515 ms

site_main.js

site_main.js

1517 ms

awdr-dynamic-price.js

awdr-dynamic-price.js

1519 ms

custom.js

custom.js

1567 ms

index.js

index.js

1581 ms

webpack.runtime.min.js

webpack.runtime.min.js

1589 ms

frontend-modules.min.js

frontend-modules.min.js

1521 ms

core.min.js

core.min.js

1524 ms

frontend.min.js

frontend.min.js

1526 ms

fa-brands-400.woff

fa-brands-400.woff

1580 ms

fa-brands-400.ttf

fa-brands-400.ttf

1584 ms

auxin-front.woff

auxin-front.woff

1599 ms

custom.css

custom.css

1519 ms

cropped-crystal-forum-logo_100px.png

cropped-crystal-forum-logo_100px.png

1535 ms

crystal-forum-logo_100px.png

crystal-forum-logo_100px.png

1531 ms

downarrow.svg

downarrow.svg

1593 ms

empty-cart.svg

empty-cart.svg

1591 ms

back.png

back.png

1594 ms

PosterBee-trans3.png

PosterBee-trans3.png

1535 ms

Preciosa-image-02-768x768.png

Preciosa-image-02-768x768.png

1524 ms

symbols.svg

symbols.svg

1535 ms

preciosa-image-01.jpg

preciosa-image-01.jpg

1603 ms

image002.png

image002.png

1622 ms

Bee-home-page-2-e1648547137541.jpg

Bee-home-page-2-e1648547137541.jpg

1586 ms

recaptcha__en.js

recaptcha__en.js

23 ms

woocommerce-smallscreen.css

woocommerce-smallscreen.css

255 ms

SEO Factors

crystalforum.co.za SEO score

0

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 Crystalforum.co.za 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 Crystalforum.co.za 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

crystalforum.co.za

Open Graph data is detected on the main page of Crystal Forum. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: