Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 62

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

talker.news

News and Data-Driven Content for journalists - Talker

Page Load Speed

10 sec in total

First Response

625 ms

Resources Loaded

8.4 sec

Page Rendered

939 ms

talker.news screenshot

About Website

Visit talker.news now to see the best up-to-date Talker content and also check out these interesting facts you probably never knew about talker.news

talker.news delivers ready-to-use news and content to journalists, editors, writers and producers. Our stories are easy to find and quick to download.

Visit talker.news

Key Findings

We analyzed Talker.news page load time and found that the first response time was 625 ms and then it took 9.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

talker.news performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

38/100

10%

LCP (Largest Contentful Paint)

Value37.8 s

0/100

25%

SI (Speed Index)

Value15.7 s

0/100

10%

TBT (Total Blocking Time)

Value5,530 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.134

80/100

15%

TTI (Time to Interactive)

Value48.9 s

0/100

10%

Network Requests Diagram

talker.news

625 ms

autoptimize_a9279a299b7eae93e53f521df04cf068.css

52 ms

css

31 ms

dashicons.min.css

25 ms

all.css

167 ms

Our browser made a total of 268 requests to load all elements on the main page. We found that 86% of them (231 requests) were addressed to the original Talker.news, 2% (6 requests) were made to Use.fontawesome.com and 2% (6 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Talker.news.

Page Optimization Overview & Recommendations

Page size can be reduced by 466.5 kB (11%)

Content Size

4.2 MB

After Optimization

3.8 MB

In fact, the total size of Talker.news main page is 4.2 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. 85% 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 3.2 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 281.1 kB

  • Original 325.5 kB
  • After minification 325.5 kB
  • After compression 44.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 281.1 kB or 86% of the original size.

Image Optimization

-2%

Potential reduce by 53.0 kB

  • Original 3.2 MB
  • After minification 3.1 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. Talker images are well optimized though.

JavaScript Optimization

-3%

Potential reduce by 14.8 kB

  • Original 510.2 kB
  • After minification 510.2 kB
  • After compression 495.4 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

-49%

Potential reduce by 117.6 kB

  • Original 238.0 kB
  • After minification 121.4 kB
  • After compression 120.4 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. Talker.news needs all CSS files to be minified and compressed as it can save up to 117.6 kB or 49% of the original size.

Requests Breakdown

Number of requests can be reduced by 24 (9%)

Requests Now

257

After Optimization

233

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

Accessibility Review

talker.news accessibility score

62

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

[id] attributes on active, focusable elements are not unique

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

Form elements do not have associated labels

High

Links do not have a discernible name

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

talker.news 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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

talker.news SEO score

92

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

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 Talker.news 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 Talker.news 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 Talker. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: