Tools & Wizards About Us
talisa.com.au screenshot

Report Summary

  • 3

    Performance

    Renders faster than
    20% of other websites

  • 63

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 84

    SEO

    Google-friendlier than
    53% of websites

talisa.com.au

Talisa Jewellery - designer rings, necklaces and bracelets

Page Load Speed

963 ms in total

First Response

25 ms

Resources Loaded

525 ms

Page Rendered

413 ms

talisa.com.au screenshot

About Website

Click here to check amazing Talisa content for Australia. Otherwise, check out these important facts you probably never knew about talisa.com.au

Where Jewellery and Creativity Connect. Personalised jewellery is a deep and meaningful way to express love and also to tell a story.

Visit talisa.com.au

Key Findings

We analyzed Talisa.com.au page load time and found that the first response time was 25 ms and then it took 938 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

talisa.com.au performance score

3

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.8 s

11/100

10%

LCP (Largest Contentful Paint)

Value16.2 s

0/100

25%

SI (Speed Index)

Value10.7 s

7/100

10%

TBT (Total Blocking Time)

Value2,790 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.774

5/100

15%

TTI (Time to Interactive)

Value30.1 s

0/100

10%

Network Requests Diagram

talisa.com.au

25 ms

www.talisa.com.au

50 ms

styles-m.min.css

91 ms

afterpay-express-checkout.min.css

83 ms

magnific-popup.min.css

82 ms

Our browser made a total of 43 requests to load all elements on the main page. We found that 5% of them (2 requests) were addressed to the original Talisa.com.au, 58% (25 requests) were made to Assets.talisa.com and 19% (8 requests) were made to Static.klaviyo.com. The less responsive or slowest element that took the longest time to load (194 ms) relates to the external source Assets.talisa.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 86.4 kB (9%)

Content Size

979.8 kB

After Optimization

893.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Talisa.com.au main page is 979.8 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. 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 644.5 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 75.9 kB

  • Original 94.6 kB
  • After minification 78.2 kB
  • After compression 18.8 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 16.5 kB, which is 17% 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 75.9 kB or 80% of the original size.

Image Optimization

-1%

Potential reduce by 5.8 kB

  • Original 644.5 kB
  • After minification 638.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. Talisa images are well optimized though.

JavaScript Optimization

-4%

Potential reduce by 4.4 kB

  • Original 110.7 kB
  • After minification 110.7 kB
  • After compression 106.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. This website has mostly compressed JavaScripts.

CSS Optimization

-0%

Potential reduce by 229 B

  • Original 130.0 kB
  • After minification 130.0 kB
  • After compression 129.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. Talisa.com.au has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 25 (69%)

Requests Now

36

After Optimization

11

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

talisa.com.au

talisa.com.au

25 ms

www.talisa.com.au

www.talisa.com.au

50 ms

styles-m.min.css

styles-m.min.css

91 ms

afterpay-express-checkout.min.css

afterpay-express-checkout.min.css

83 ms

magnific-popup.min.css

magnific-popup.min.css

82 ms

styles-l.min.css

styles-l.min.css

139 ms

css2

css2

138 ms

logo-au-206x104.png

logo-au-206x104.png

87 ms

redirect.min.js

redirect.min.js

132 ms

require.min.js

require.min.js

78 ms

requirejs-min-resolver.min.js

requirejs-min-resolver.min.js

83 ms

mixins.min.js

mixins.min.js

171 ms

requirejs-config-common.min.js

requirejs-config-common.min.js

174 ms

requirejs-config-cms.min.js

requirejs-config-cms.min.js

175 ms

requirejs-config.min.js

requirejs-config.min.js

173 ms

klaviyo.js

klaviyo.js

168 ms

dt-jewelry-gold.jpg

dt-jewelry-gold.jpg

192 ms

dt-necklaces-small-gold1.jpg

dt-necklaces-small-gold1.jpg

189 ms

dt-bracelets-small-gold.jpg

dt-bracelets-small-gold.jpg

192 ms

dt-rings-small-gold.jpg

dt-rings-small-gold.jpg

190 ms

dt-men-small_fath_circle_gold.jpg

dt-men-small_fath_circle_gold.jpg

193 ms

dt-new_necklaces.jpg

dt-new_necklaces.jpg

194 ms

dt-gift_card.jpg

dt-gift_card.jpg

193 ms

select-bg.svg

select-bg.svg

45 ms

S6uyw4BMUTPHvxk.ttf

S6uyw4BMUTPHvxk.ttf

98 ms

S6u9w4BMUTPHh7USew8.ttf

S6u9w4BMUTPHh7USew8.ttf

109 ms

S6u9w4BMUTPHh6UVew8.ttf

S6u9w4BMUTPHh6UVew8.ttf

128 ms

gtm.js

gtm.js

150 ms

matomo.js

matomo.js

123 ms

bundle-common.min.js

bundle-common.min.js

76 ms

fender_analytics.739eafc699de20b4c3bb.js

fender_analytics.739eafc699de20b4c3bb.js

92 ms

static.047f24ade89e4aff54a9.js

static.047f24ade89e4aff54a9.js

93 ms

runtime.242037525aa1c76dfe9b.js

runtime.242037525aa1c76dfe9b.js

10 ms

sharedUtils.a2ead10f1141521a8e3e.js

sharedUtils.a2ead10f1141521a8e3e.js

62 ms

vendors~signup_forms~post_identification_sync~web_personalization~reviews~atlas.3ee75b12730991c4d04b.js

vendors~signup_forms~post_identification_sync~web_personalization~reviews~atlas.3ee75b12730991c4d04b.js

61 ms

vendors~signup_forms~onsite-triggering.a2030eb5abe19f808c94.js

vendors~signup_forms~onsite-triggering.a2030eb5abe19f808c94.js

18 ms

vendors~signup_forms.e707d6d405eecdf67185.js

vendors~signup_forms.e707d6d405eecdf67185.js

60 ms

default~signup_forms~onsite-triggering.ddf307d73959ae2a00ef.js

default~signup_forms~onsite-triggering.ddf307d73959ae2a00ef.js

60 ms

signup_forms.5828d30d7aa945da8745.js

signup_forms.5828d30d7aa945da8745.js

59 ms

Luma-Icons.woff

Luma-Icons.woff

24 ms

fa-brands-400.woff

fa-brands-400.woff

45 ms

print.min.css

print.min.css

8 ms

bundle-common.min.js

bundle-common.min.js

52 ms

Accessibility Review

talisa.com.au accessibility score

63

Accessibility Issues

ARIA

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.

Impact

Issue

High

[role]s do not have all required [aria-*] attributes

High

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

High

[role]s are not contained by their required parent element

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Tables and lists

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

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

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

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

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

Best Practices

talisa.com.au best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

talisa.com.au SEO score

84

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

Content Best Practices

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

Impact

Issue

High

Image elements do not have [alt] attributes

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

High

Tap targets are not sized appropriately

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 Talisa.com.au 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 Talisa.com.au 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

talisa.com.au

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