Report Summary

  • 42

    Performance

    Renders faster than
    61% of other websites

  • 64

    Accessibility

    Visual factors better than
    that of 29% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

talk2.media

Talk2 Media & Events | Australian Consumer Events & Trade Show Organiser

Page Load Speed

3.1 sec in total

First Response

77 ms

Resources Loaded

2.9 sec

Page Rendered

123 ms

talk2.media screenshot

About Website

Visit talk2.media now to see the best up-to-date Talk2 content and also check out these interesting facts you probably never knew about talk2.media

Australia's leading organiser of consumer and trade exhibitions and events including Good Food & Wine Show, AIME and Power + Utilities Australia.

Visit talk2.media

Key Findings

We analyzed Talk2.media page load time and found that the first response time was 77 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

talk2.media performance score

42

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

38/100

10%

LCP (Largest Contentful Paint)

Value14.4 s

0/100

25%

SI (Speed Index)

Value10.7 s

7/100

10%

TBT (Total Blocking Time)

Value140 ms

96/100

30%

CLS (Cumulative Layout Shift)

Value0.253

49/100

15%

TTI (Time to Interactive)

Value12.2 s

15/100

10%

Network Requests Diagram

talk2.media

77 ms

talk2.media

127 ms

site.min.css

842 ms

styles.css

638 ms

owl.carousel.min.css

637 ms

Our browser made a total of 23 requests to load all elements on the main page. We found that 78% of them (18 requests) were addressed to the original Talk2.media, 9% (2 requests) were made to Google-analytics.com and 4% (1 request) were made to Google.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Talk2.media.

Page Optimization Overview & Recommendations

Page size can be reduced by 968.5 kB (20%)

Content Size

4.8 MB

After Optimization

3.8 MB

In fact, the total size of Talk2.media main page is 4.8 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. 20% of websites need less resources to load. Images take 3.7 MB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 16.5 kB

  • Original 22.0 kB
  • After minification 18.7 kB
  • After compression 5.5 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 3.3 kB, which is 15% 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 16.5 kB or 75% of the original size.

Image Optimization

-7%

Potential reduce by 250.5 kB

  • Original 3.7 MB
  • After minification 3.5 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. Talk2 images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 670.0 kB

  • Original 1.0 MB
  • After minification 549.6 kB
  • After compression 330.8 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 670.0 kB or 67% of the original size.

CSS Optimization

-84%

Potential reduce by 31.5 kB

  • Original 37.7 kB
  • After minification 29.0 kB
  • After compression 6.1 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. Talk2.media needs all CSS files to be minified and compressed as it can save up to 31.5 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 10 (48%)

Requests Now

21

After Optimization

11

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

Accessibility Review

talk2.media accessibility score

64

Accessibility Issues

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.

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

talk2.media best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

talk2.media SEO score

93

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

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

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 Talk2.media 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 Talk2.media 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

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