Report Summary

  • 29

    Performance

    Renders faster than
    49% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

omnibusz.blog.hu

Omnibusz

Page Load Speed

16.8 sec in total

First Response

277 ms

Resources Loaded

7.6 sec

Page Rendered

8.9 sec

omnibusz.blog.hu screenshot

About Website

Welcome to omnibusz.blog.hu homepage info - get ready to check Omnibusz Blog best content for Hungary right away, or after learning these important things about omnibusz.blog.hu

Hírek, érdekességek az autóbuszok világából.

Visit omnibusz.blog.hu

Key Findings

We analyzed Omnibusz.blog.hu page load time and found that the first response time was 277 ms and then it took 16.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

omnibusz.blog.hu performance score

29

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.2 s

8/100

10%

LCP (Largest Contentful Paint)

Value11.2 s

0/100

25%

SI (Speed Index)

Value10.8 s

6/100

10%

TBT (Total Blocking Time)

Value360 ms

72/100

30%

CLS (Cumulative Layout Shift)

Value0.345

32/100

15%

TTI (Time to Interactive)

Value12.7 s

14/100

10%

Network Requests Diagram

omnibusz.blog.hu

277 ms

blog_def.min.css

256 ms

styles.css

226 ms

blog.min.css

257 ms

galeria.css

256 ms

Our browser made a total of 205 requests to load all elements on the main page. We found that 3% of them (6 requests) were addressed to the original Omnibusz.blog.hu, 21% (43 requests) were made to Facebook.com and 21% (43 requests) were made to M.cdn.blog.hu. The less responsive or slowest element that took the longest time to load (1.6 sec) relates to the external source M.cdn.blog.hu.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.4 MB (15%)

Content Size

9.0 MB

After Optimization

7.7 MB

In fact, the total size of Omnibusz.blog.hu main page is 9.0 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 8.1 MB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 344.8 kB

  • Original 385.8 kB
  • After minification 329.0 kB
  • After compression 41.1 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 56.9 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 344.8 kB or 89% of the original size.

Image Optimization

-8%

Potential reduce by 617.8 kB

  • Original 8.1 MB
  • After minification 7.4 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. Omnibusz Blog images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 199.6 kB

  • Original 310.8 kB
  • After minification 308.8 kB
  • After compression 111.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 199.6 kB or 64% of the original size.

CSS Optimization

-75%

Potential reduce by 199.0 kB

  • Original 265.4 kB
  • After minification 254.0 kB
  • After compression 66.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. Omnibusz.blog.hu needs all CSS files to be minified and compressed as it can save up to 199.0 kB or 75% of the original size.

Requests Breakdown

Number of requests can be reduced by 75 (47%)

Requests Now

160

After Optimization

85

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

Accessibility Review

omnibusz.blog.hu accessibility score

81

Accessibility Issues

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

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

omnibusz.blog.hu best practices score

75

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

Browser errors were logged to the console

SEO Factors

omnibusz.blog.hu SEO score

86

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

Language and Encoding

  • Language Detected

    HU

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Omnibusz.blog.hu can be misinterpreted by Google and other search engines. Our service has detected that Hungarian is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Omnibusz.blog.hu 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 Omnibusz Blog. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: