Access 24hours.bg. Новините, мненията и историите, каквито са | 24 Часа

24hours.bg screenshot

16

Performance

Renders faster than
30% of other websites
96

Accessibility

Visual factors better than
that of 89% of websites
75

Best Practices

More advanced features
available than in
36% of websites
95

SEO

Google-friendlier than
91% of websites

First Response

788 ms

Resources Loaded

11.5 sec

Page Rendered

120.1 sec

24hours.bg screenshot

About Website

Click here to check amazing 24 Hours content. Otherwise, check out these important facts you probably never knew about 24hours.bg

Новини, мнения, коментари, анализи, интервюта, разследвания, бизнес информация, спорт, здраве, забавни четива, времето, справочник, истории, оживление с 24chasa.bg

Visit 24hours.bg

Key Findings

We analyzed 24hours.bg page load time and found that the first response time was 788 ms and then it took 131.6 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.

name

value

score

weighting

FCP (First Contentful Paint)

Value5.4 s

7/100

10%

LCP (Largest Contentful Paint)

Value9.7 s

0/100

25%

SI (Speed Index)

Value45.2 s

0/100

10%

TBT (Total Blocking Time)

Value90,130 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value119.9 s

0/100

10%

www.24chasa.bg

788 ms

css2

501 ms

bootstrap-icons.css

610 ms

swiper-bundle.css

609 ms

theme.css

340 ms

Our browser made a total of 200 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original 24hours.bg, 39% (78 requests) were made to Cache2.24chasa.bg and 10% (20 requests) were made to 24chasa.bg. The less responsive or slowest element that took the longest time to load (6.6 sec) relates to the external source Cache1.24chasa.bg.

Content Size

4.1 MB

After Optimization

3.7 MB

In fact, the total size of 24hours.bg main page is 4.1 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.7 MB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 265.4 kB

Original 306.4 kB
After minification 306.3 kB
After compression 41.0 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 265.4 kB or 87% of the original size.

Image Optimization

-3%

Potential reduce by 122.2 kB

Original 3.7 MB
After minification 3.6 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. 24 Hours images are well optimized though.

JavaScript Optimization

-48%

Potential reduce by 21.3 kB

Original 44.9 kB
After minification 44.9 kB
After compression 23.6 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 21.3 kB or 48% of the original size.

CSS Optimization

-0%

Potential reduce by 0 B

Original 21.5 kB
After minification 21.5 kB
After compression 21.5 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. 24hours.bg has all CSS files already compressed.

Requests Now

198

After Optimization

182

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

Accessibility Issues

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 the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

High

<frame> or <iframe> elements do not have a title

Areas of Improvement

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

Search Engine Optimization Advices

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

High

Tap targets are not sized appropriately

Language and Encoding

Language Detected

BG
Language Claimed

EN
Encoding

UTF-8

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

24hours.bg

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