Tools & Wizards About Us
szelessav.net screenshot

Report Summary

  • 43

    Performance

    Renders faster than
    62% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 49% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

szelessav.net

Szolgáltatóktól független internetes sebességmérés ‐ Szélessáv.net

Page Load Speed

6.3 sec in total

First Response

735 ms

Resources Loaded

5.3 sec

Page Rendered

255 ms

szelessav.net screenshot

About Website

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

Sebességteszt. Tesztelje sávszélességét. Mérje meg, milyen gyors az internete, elemezze a vezetékes és a mobilinternet-hálózatok országos adatait.

Visit szelessav.net

Key Findings

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

Performance Metrics

szelessav.net performance score

43

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.7 s

0/100

10%

LCP (Largest Contentful Paint)

Value12.2 s

0/100

25%

SI (Speed Index)

Value10.0 s

9/100

10%

TBT (Total Blocking Time)

Value230 ms

87/100

30%

CLS (Cumulative Layout Shift)

Value0.023

100/100

15%

TTI (Time to Interactive)

Value13.7 s

10/100

10%

Network Requests Diagram

szelessav.net

735 ms

hu

293 ms

jquery-2.1.1.min.js

675 ms

jquery.form_3.46.js

344 ms

jquery.cookie.js

345 ms

Our browser made a total of 69 requests to load all elements on the main page. We found that 96% of them (66 requests) were addressed to the original Szelessav.net, 3% (2 requests) were made to Google-analytics.com and 1% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Szelessav.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 60.9 kB (3%)

Content Size

1.9 MB

After Optimization

1.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Szelessav.net main page is 1.9 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. 25% of websites need less resources to load. Images take 1.6 MB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 17.1 kB

  • Original 23.8 kB
  • After minification 23.4 kB
  • After compression 6.7 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 17.1 kB or 72% of the original size.

Image Optimization

-2%

Potential reduce by 24.8 kB

  • Original 1.6 MB
  • After minification 1.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. Szelessav images are well optimized though.

JavaScript Optimization

-3%

Potential reduce by 7.2 kB

  • Original 257.9 kB
  • After minification 257.9 kB
  • After compression 250.7 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

-17%

Potential reduce by 11.9 kB

  • Original 68.5 kB
  • After minification 68.4 kB
  • After compression 56.6 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. Szelessav.net needs all CSS files to be minified and compressed as it can save up to 11.9 kB or 17% of the original size.

Requests Breakdown

Number of requests can be reduced by 45 (67%)

Requests Now

67

After Optimization

22

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

szelessav.net

szelessav.net

735 ms

hu

hu

293 ms

jquery-2.1.1.min.js

jquery-2.1.1.min.js

675 ms

jquery.form_3.46.js

jquery.form_3.46.js

344 ms

jquery.cookie.js

jquery.cookie.js

345 ms

jquery-ui-12.min.js

jquery-ui-12.min.js

589 ms

iframeResizer.min.js

iframeResizer.min.js

346 ms

jquery.jtable.min.js

jquery.jtable.min.js

467 ms

JS_hu.nof

JS_hu.nof

460 ms

nmhh.css

nmhh.css

458 ms

jquery.tablesorter.pager.css

jquery.tablesorter.pager.css

459 ms

jquery.tablesorter_hu.js

jquery.tablesorter_hu.js

701 ms

jquery.tablesorter.widgets.js

jquery.tablesorter.widgets.js

702 ms

widget-print.js

widget-print.js

573 ms

jquery.tablesorter.pager_hu.js

jquery.tablesorter.pager_hu.js

704 ms

jquery-ui.min.js

jquery-ui.min.js

820 ms

jquery-ui.css

jquery-ui.css

814 ms

chosen.jquery.min.js

chosen.jquery.min.js

790 ms

chosen.css

chosen.css

800 ms

icheck.js

icheck.js

801 ms

nmhh.css

nmhh.css

810 ms

blue.css

blue.css

904 ms

jquery-ui-1.8.16.custom.css

jquery-ui-1.8.16.custom.css

916 ms

jtable.css

jtable.css

917 ms

responsiveslides.min.js

responsiveslides.min.js

925 ms

cookiechoices.js

cookiechoices.js

927 ms

loading.gif

loading.gif

232 ms

Desktop.css

Desktop.css

296 ms

analytics.js

analytics.js

33 ms

header_bg.png

header_bg.png

115 ms

footer_bg.png

footer_bg.png

113 ms

home_icon_40x40px.png

home_icon_40x40px.png

114 ms

login_separator.png

login_separator.png

115 ms

menuikon.png

menuikon.png

116 ms

menukeres_ikon.png

menukeres_ikon.png

116 ms

spacer.png

spacer.png

225 ms

en.png

en.png

226 ms

szelessav_net_logo_inverz.png

szelessav_net_logo_inverz.png

228 ms

NMHH_logo_inverz.png

NMHH_logo_inverz.png

339 ms

ikon_sebesseg.png

ikon_sebesseg.png

217 ms

menu_sep_bg.png

menu_sep_bg.png

219 ms

top_keres_bg.png

top_keres_bg.png

329 ms

szelessav_net_logo.png

szelessav_net_logo.png

442 ms

menu2_home_bg.png

menu2_home_bg.png

330 ms

menu2_bg_nyil.png

menu2_bg_nyil.png

330 ms

file.nof

file.nof

562 ms

start_tudta_ny_bg.png

start_tudta_ny_bg.png

440 ms

file.nof

file.nof

559 ms

file.nof

file.nof

892 ms

file.nof

file.nof

2136 ms

start_sebesseg_bg.png

start_sebesseg_bg.png

553 ms

start_main_bg.png

start_main_bg.png

777 ms

start_main_p_bg.png

start_main_p_bg.png

889 ms

start_reg_ny_bg.png

start_reg_ny_bg.png

674 ms

start_tudta_bg.png

start_tudta_bg.png

789 ms

start_nyil_w_bg.png

start_nyil_w_bg.png

789 ms

file.nof

file.nof

1007 ms

meroauto.png

meroauto.png

1013 ms

start_box_g_bg.png

start_box_g_bg.png

1129 ms

start_sem_g_bg.png

start_sem_g_bg.png

1223 ms

start_sem_ny_bg.png

start_sem_ny_bg.png

1004 ms

reg_kek_blokk_bg.png

reg_kek_blokk_bg.png

1117 ms

fel_nyil.png

fel_nyil.png

1102 ms

themes.gif

themes.gif

1108 ms

collect

collect

12 ms

js

js

71 ms

print.css

print.css

115 ms

Mobil.css

Mobil.css

233 ms

Tablet.css

Tablet.css

237 ms

Accessibility Review

szelessav.net accessibility score

80

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

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

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

Links do not have a discernible name

Best Practices

szelessav.net best practices score

67

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

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

szelessav.net SEO score

91

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

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

    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 Szelessav.net 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 Szelessav.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

szelessav.net

Open Graph description is not detected on the main page of Szelessav. 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: