6.5 sec in total
387 ms
5.7 sec
375 ms
Visit countess.hupont.hu now to see the best up-to-date Countess Hupont content for Hungary and also check out these interesting facts you probably never knew about countess.hupont.hu
A gróf BREDA és a VÁSÁRHELYI család genealógiája - Gyevnár Erika tollából - A múlt poros polcain kutatva néhol mégis megcsillan egy név, egy homályos emlék...
Visit countess.hupont.huWe analyzed Countess.hupont.hu page load time and found that the first response time was 387 ms and then it took 6.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
countess.hupont.hu performance score
name
value
score
weighting
Value2.0 s
84/100
10%
Value4.3 s
42/100
25%
Value2.6 s
97/100
10%
Value1,050 ms
25/100
30%
Value0
100/100
15%
Value7.5 s
48/100
10%
387 ms
607 ms
481 ms
501 ms
502 ms
Our browser made a total of 51 requests to load all elements on the main page. We found that 35% of them (18 requests) were addressed to the original Countess.hupont.hu, 14% (7 requests) were made to Tpc.googlesyndication.com and 12% (6 requests) were made to Hupont.hu. The less responsive or slowest element that took the longest time to load (4.7 sec) belongs to the original domain Countess.hupont.hu.
Page size can be reduced by 636.2 kB (35%)
1.8 MB
1.2 MB
In fact, the total size of Countess.hupont.hu main page is 1.8 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. 50% of websites need less resources to load. Javascripts take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 33.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 33.7 kB or 74% of the original size.
Potential reduce by 2.7 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. Countess Hupont images are well optimized though.
Potential reduce by 599.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 599.9 kB or 54% of the original size.
Number of requests can be reduced by 32 (67%)
48
16
The browser has sent 48 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Countess Hupont. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and as a result speed up the page load time.
countess.hupont.hu
387 ms
jquery-1.7.2.min.js
607 ms
jquery.cookie.js
481 ms
jquery.tipTip.minified.js
501 ms
javascript.js
502 ms
AC_RunActiveContent.js
504 ms
stilus.css
144 ms
adsbygoogle.js
142 ms
adsbygoogle.js
240 ms
js
58 ms
tartalom_hatter.gif
141 ms
kereso_doboz.gif
128 ms
felso_arnyek.gif
4303 ms
felso_arnyek_bal.gif
4479 ms
felso_keret.gif
4478 ms
felso_arnyek_jobb.gif
4481 ms
fejleckep.png
4710 ms
fejlec.gif
244 ms
menu_felso_keret.gif
496 ms
menu_also_keret.gif
614 ms
ep_la_gazette_desprit_xviii_6879_1626182380976400_3622393954571567392_n.png
1741 ms
vasarhelyi_cimer.jpg
1973 ms
bz-p4gewkkgrhqrjoew5tuebhbmv7iebsw_12.jpg
2093 ms
show_ads_impl.js
261 ms
also_arnyek_bal.gif
2046 ms
also_keret.gif
2163 ms
also_arnyek_jobb.gif
2282 ms
also_arnyek.gif
2400 ms
zrt_lookup.html
41 ms
ads
431 ms
ads
401 ms
ads
427 ms
ads
339 ms
reactive_library.js
146 ms
ca-pub-6270525616381872
68 ms
3052336590256276155
161 ms
load_preloaded_resource.js
31 ms
icon.png
22 ms
abg_lite.js
32 ms
window_focus.js
38 ms
qs_click_protection.js
42 ms
ufs_web_display.js
25 ms
3ce8c4eab42230976bac8dfb895e1176.js
148 ms
fullscreen_api_adapter.js
32 ms
interstitial_ad_frame.js
137 ms
feedback_grey600_24dp.png
140 ms
settings_grey600_24dp.png
150 ms
css
42 ms
4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrw2IJllpyw.ttf
21 ms
4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrwEIJllpyw.ttf
25 ms
wJiNEMIFAPB28UFvxM_UYtYFK_ILnv1_rxRzUTsn-Pg.js
4 ms
countess.hupont.hu accessibility score
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
countess.hupont.hu 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
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
countess.hupont.hu 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
![]()
HU
![]()
HU
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Countess.hupont.hu can be misinterpreted by Google and other search engines. Our service has detected that Hungarian is used on the page, and it matches the claimed language. Our system also found out that Countess.hupont.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.
countess.hupont.hu
Open Graph description is not detected on the main page of Countess Hupont. 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: