Report Summary

  • 15

    Performance

    Renders faster than
    28% of other websites

  • 50

    Accessibility

    Visual factors better than
    that of 20% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

prajavani.net

Prajavani | ಪ್ರಜಾವಾಣಿ ತಾಜಾ ಸುದ್ದಿ, ಸಮಾಚಾರ, ವಾರ್ತೆ, ಕರ್ನಾಟಕ, ಬೆಂಗಳೂರು, ರಾಜ್ಯ, ರಾಷ್ಟ್ರೀಯ, ವಿದೇಶ ಸುದ್ದಿಗಳು Latest News Headlines from Bengaluru, Karnatak...

Page Load Speed

19.2 sec in total

First Response

138 ms

Resources Loaded

5 sec

Page Rendered

14.1 sec

prajavani.net screenshot

About Website

Visit prajavani.net now to see the best up-to-date Prajavani content for India and also check out these interesting facts you probably never knew about prajavani.net

Prajavani | Find Trending Latest News in Kannada. Read Today's Top Karnataka State News from Bengaluru, Mangalore, Hubli-Dharwad, Mysore & India on Politics, Election, Sports and Cinema ಪ್ರಜಾವಾಣಿ...

Visit prajavani.net

Key Findings

We analyzed Prajavani.net page load time and found that the first response time was 138 ms and then it took 19.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.

Performance Metrics

prajavani.net performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

24/100

10%

LCP (Largest Contentful Paint)

Value15.2 s

0/100

25%

SI (Speed Index)

Value9.9 s

10/100

10%

TBT (Total Blocking Time)

Value5,300 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.14

79/100

15%

TTI (Time to Interactive)

Value27.0 s

0/100

10%

Network Requests Diagram

prajavani.net

138 ms

www.prajavani.net

156 ms

css_lQaZfjVpwP_oGNqdtWCSpJT1EMqXdMiU84ekLLxQnc4.css

68 ms

css_4gBXBPHKsdX1v-XfpSCC52iCkB4S9Yn5SA50cpYHk5c.css

69 ms

css_KpHsFsHL5G3x9EUJr5pMqQKsGs4fdCXEGrY6HhOgLHA.css

71 ms

Our browser made a total of 194 requests to load all elements on the main page. We found that 66% of them (129 requests) were addressed to the original Prajavani.net, 7% (13 requests) were made to Webclient.cricbuzz.com and 4% (7 requests) were made to Googleads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Prajavani.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 916.1 kB (37%)

Content Size

2.5 MB

After Optimization

1.6 MB

In fact, the total size of Prajavani.net 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. 75% 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.3 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 280.5 kB

  • Original 330.1 kB
  • After minification 303.6 kB
  • After compression 49.6 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 280.5 kB or 85% of the original size.

Image Optimization

-2%

Potential reduce by 28.2 kB

  • Original 1.3 MB
  • After minification 1.3 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. Prajavani images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 459.9 kB

  • Original 665.8 kB
  • After minification 556.4 kB
  • After compression 205.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 459.9 kB or 69% of the original size.

CSS Optimization

-80%

Potential reduce by 147.5 kB

  • Original 183.4 kB
  • After minification 174.4 kB
  • After compression 35.9 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. Prajavani.net needs all CSS files to be minified and compressed as it can save up to 147.5 kB or 80% of the original size.

Requests Breakdown

Number of requests can be reduced by 74 (40%)

Requests Now

186

After Optimization

112

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

Accessibility Review

prajavani.net accessibility score

50

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

[aria-*] attributes do not match their roles

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

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

prajavani.net best practices score

58

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

prajavani.net SEO score

77

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

Links do not have descriptive text

High

Image elements do not have [alt] attributes

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

    KN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Prajavani.net can be misinterpreted by Google and other search engines. Our service has detected that Kannada is used on the page, and it does not match the claimed English language. Our system also found out that Prajavani.net 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 description is not detected on the main page of Prajavani. 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: