Access aurex.co.zw. Home - Aurex Jewellery

name

value

score

weighting

FCP (First Contentful Paint)

Value6.6 s

2/100

10%

LCP (Largest Contentful Paint)

Value20.1 s

0/100

25%

SI (Speed Index)

Value12.8 s

2/100

10%

TBT (Total Blocking Time)

Value1,330 ms

17/100

30%

CLS (Cumulative Layout Shift)

Value0.139

79/100

15%

TTI (Time to Interactive)

Value18.4 s

3/100

10%

aurex.co.zw

451 ms

js

83 ms

wp-emoji-release.min.js

93 ms

layerslider.css

177 ms

styles.css

250 ms

Our browser made a total of 117 requests to load all elements on the main page. We found that 68% of them (80 requests) were addressed to the original Aurex.co.zw, 11% (13 requests) were made to Fonts.gstatic.com and 7% (8 requests) were made to Embed.tawk.to. The less responsive or slowest element that took the longest time to load (822 ms) belongs to the original domain Aurex.co.zw.

Content Size

2.5 MB

After Optimization

2.1 MB

In fact, the total size of Aurex.co.zw main page is 2.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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.0 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 124.5 kB

Original 156.2 kB
After minification 152.1 kB
After compression 31.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 124.5 kB or 80% of the original size.

Image Optimization

-8%

Potential reduce by 85.1 kB

Original 1.0 MB
After minification 959.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. Aurex images are well optimized though.

JavaScript Optimization

-11%

Potential reduce by 104.4 kB

Original 918.3 kB
After minification 918.2 kB
After compression 813.9 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 104.4 kB or 11% of the original size.

CSS Optimization

-20%

Potential reduce by 79.1 kB

Original 392.9 kB
After minification 392.1 kB
After compression 313.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. Aurex.co.zw needs all CSS files to be minified and compressed as it can save up to 79.1 kB or 20% of the original size.

Requests Now

After Optimization

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

Accessibility Issues

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

These are opportunities to improve keyboard navigation in your application.

High

Heading elements are not in a sequentially-descending order

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.

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

These items highlight common accessibility best practices.

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

High

Serves images with low resolution

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

Search Engine Optimization Advices

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

High

Links are not crawlable

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

High

Image elements do not have [alt] attributes

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/).

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 Aurex.co.zw 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 Aurex.co.zw 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

aurex.co.zw

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

Report Summary

Performance

Accessibility

Best Practices

SEO

Home - Aurex Jewellery

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

aurex.co.zw

js

wp-emoji-release.min.js

layerslider.css

styles.css

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

aurex.co.zw

js

wp-emoji-release.min.js

layerslider.css

styles.css

form_style.css

all.min.css

bootstrap.min.css

front.css

go_pricing_styles.css

dashicons.min.css

frontend.css

tp_twitter_plugin.css

settings.css

slick.css

wpls-public.css

front.min.css

sassy-social-share-public.css

js_composer.min.css

css

main.min.css

back-compat.min.css

all.css

fontello.min.css

post-type.css

custom.css

media.css

post-type-dynamic.css

style.css

Defaults.css

style.min.css

jquery.js

jquery-migrate.min.js

greensock.js

layerslider.kreaturamedia.jquery.js

layerslider.transitions.js

frontend-gtag.min.js

bootstrap.bundle.min.js

TweenMax.min.js

js

css

css

css