6.3 sec in total
731 ms
4.9 sec
665 ms
Click here to check amazing Tenyleg content for Hungary. Otherwise, check out these important facts you probably never knew about tenyleg.com
Visit tenyleg.comWe analyzed Tenyleg.com page load time and found that the first response time was 731 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.
tenyleg.com performance score
name
value
score
weighting
Value17.7 s
0/100
10%
Value28.7 s
0/100
25%
Value22.4 s
0/100
10%
Value3,470 ms
2/100
30%
Value0.295
40/100
15%
Value24.6 s
0/100
10%
731 ms
200 ms
392 ms
244 ms
38 ms
Our browser made a total of 124 requests to load all elements on the main page. We found that 4% of them (5 requests) were addressed to the original Tenyleg.com, 86% (107 requests) were made to Blueray.blob.core.windows.net and 3% (4 requests) were made to Maps.google.com. The less responsive or slowest element that took the longest time to load (2.1 sec) relates to the external source Blueray.blob.core.windows.net.
Page size can be reduced by 837.0 kB (67%)
1.2 MB
408.0 kB
In fact, the total size of Tenyleg.com main page is 1.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. 70% of websites need less resources to load. Javascripts take 824.3 kB which makes up the majority of the site volume.
Potential reduce by 57.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. 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 57.1 kB or 76% of the original size.
Potential reduce by 169.6 kB
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. Obviously, Tenyleg needs image optimization as it can save up to 169.6 kB or 53% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 590.3 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 590.3 kB or 72% of the original size.
Potential reduce by 20.0 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. Tenyleg.com needs all CSS files to be minified and compressed as it can save up to 20.0 kB or 79% of the original size.
Number of requests can be reduced by 29 (45%)
64
35
The browser has sent 64 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Tenyleg. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
tenyleg.com
731 ms
fontface.css
200 ms
screen.css
392 ms
screen_a.css
244 ms
jquery-ui.css
38 ms
jquery.image-gallery.min.css
228 ms
jquery-1.7.1.min.js
588 ms
jquery-ui-1.8.16.custom.min.js
1044 ms
jquery.cycle.all.js
501 ms
js
38 ms
jquery.gomap-1.3.2.js
494 ms
infobox.js
413 ms
mwheelIntent.js
473 ms
appsters-config.js
524 ms
appsters-api.js
583 ms
appsters-ui.js
705 ms
jwplayer.js
707 ms
general.css
239 ms
reset.css
301 ms
common.js
39 ms
util.js
41 ms
geocoder.js
35 ms
__header_bg_wallpaper.png
125 ms
plc_949402.png
243 ms
plc_1281590.png
169 ms
search_button_bg.png
124 ms
plc_1257018.png
654 ms
plc_1218956.png
168 ms
plc_1199613.png
331 ms
plc_1178146.png
296 ms
plc_1175178.png
344 ms
plc_1171188.png
408 ms
plc_1167329.png
367 ms
plc_1156229.png
432 ms
plc_1141502.png
468 ms
plc_1120803.png
499 ms
plc_1107994.png
547 ms
plc_1096411.png
572 ms
plc_1080907.png
569 ms
plc_1059879.png
674 ms
plc_1057555.png
657 ms
plc_1051550.png
1553 ms
plc_1046045.png
724 ms
plc_1040191.png
735 ms
plc_1010019.png
850 ms
plc_989559.png
794 ms
plc_959657.png
785 ms
plc_955359.png
888 ms
plc_947676.png
908 ms
plc_919176.png
949 ms
plc_907232.png
920 ms
plc_904985.png
940 ms
plc_888954.png
1880 ms
plc_824301.png
1262 ms
plc_806952.png
1282 ms
plc_455863.png
1164 ms
plc_446582.png
1634 ms
plc_440230.png
1297 ms
all.js
95 ms
ga.js
51 ms
plc_418426.png
1282 ms
SourceSansPro-Regular.otf
484 ms
SourceSansPro-Bold.otf
564 ms
confi-webfont.woff
394 ms
plc_412263.png
1617 ms
plc_410724.png
1586 ms
97 ms
__utm.gif
18 ms
plc_409314.png
1315 ms
xd_arbiter.php
78 ms
xd_arbiter.php
141 ms
plc_409297.png
1411 ms
plc_405086.png
1375 ms
plc_377810.png
1520 ms
plc_335190.png
1486 ms
plc_333026.png
1459 ms
plc_330466.png
1452 ms
plc_319584.png
1479 ms
plc_283675.png
2070 ms
plc_278638.png
1479 ms
plc_273112.png
1440 ms
plc_269949.png
1419 ms
plc_261759.png
1454 ms
plc_245095.png
1393 ms
plc_230071.png
1476 ms
plc_228265.png
1443 ms
plc_227983.png
1395 ms
plc_217132.png
1512 ms
plc_216045.png
1468 ms
plc_208365.png
1542 ms
plc_191615.png
1987 ms
__icon_rss.png
1977 ms
appstore_logo.png
1446 ms
Android-market-icon.png
1435 ms
win8.jpg
1491 ms
fb_logo.jpg
1506 ms
tte_logo_uj.jpg
1356 ms
tani-tani.png
1278 ms
milogo.png
1261 ms
tblog_logo.png
1316 ms
sulinet_logo_magazin.png
1230 ms
urbanlegends.png
1089 ms
bbch.jpg
1195 ms
szkeptikus.png
1074 ms
__site_bg.png
1075 ms
__header_bg.png
1061 ms
__menu_bg.png
1072 ms
bev_up.png
1069 ms
1_up.png
1003 ms
2_up.png
1011 ms
4_up.png
1057 ms
3_up.png
1050 ms
8_up.png
1030 ms
szerz_up.png
1016 ms
6_up.png
954 ms
__icon_video.png
976 ms
__icon_actuel.png
1031 ms
__line_vertical.png
977 ms
__search_box_bg.png
977 ms
__search_box.png
900 ms
__icon_next.png
910 ms
__line_horizontal.png
939 ms
__icon_contact.png
848 ms
ping
15 ms
tenyleg.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
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
Links do not have a discernible name
tenyleg.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
tenyleg.com SEO score
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
Document uses legible font sizes
Tap targets are not sized appropriately
HU
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tenyleg.com 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 Tenyleg.com 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.
tenyleg.com
Open Graph description is not detected on the main page of Tenyleg. 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: