4.5 sec in total
387 ms
3.8 sec
285 ms
Visit sg.hu now to see the best up-to-date SG content for Hungary and also check out these interesting facts you probably never knew about sg.hu
Informatika, tudomány, film és játék - hírek, cikkek, tesztek és bemutatók
Visit sg.huWe analyzed Sg.hu page load time and found that the first response time was 387 ms and then it took 4.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
sg.hu performance score
name
value
score
weighting
Value2.3 s
76/100
10%
Value8.0 s
2/100
25%
Value6.4 s
41/100
10%
Value1,910 ms
8/100
30%
Value0
100/100
15%
Value10.0 s
26/100
10%
387 ms
470 ms
323 ms
328 ms
436 ms
Our browser made a total of 77 requests to load all elements on the main page. We found that 31% of them (24 requests) were addressed to the original Sg.hu, 29% (22 requests) were made to Static.xx.fbcdn.net and 10% (8 requests) were made to Jdn.monster.com. The less responsive or slowest element that took the longest time to load (982 ms) belongs to the original domain Sg.hu.
Page size can be reduced by 333.5 kB (31%)
1.1 MB
740.3 kB
In fact, the total size of Sg.hu main page is 1.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. 45% of websites need less resources to load. Images take 647.9 kB which makes up the majority of the site volume.
Potential reduce by 31.4 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 31.4 kB or 71% of the original size.
Potential reduce by 41.9 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. SG images are well optimized though.
Potential reduce by 143.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 143.2 kB or 58% of the original size.
Potential reduce by 117.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. Sg.hu needs all CSS files to be minified and compressed as it can save up to 117.0 kB or 87% of the original size.
Number of requests can be reduced by 38 (51%)
75
37
The browser has sent 75 CSS, Javascripts, AJAX and image requests in order to completely render the main page of SG. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
sg.hu
387 ms
sg.hu
470 ms
normalize_3963487451be236bfe2f4f60ef1d1717.css
323 ms
plugins_0af53f06851499af5c5b1f6d6e57a000.css
328 ms
main_56d2985c68fd5f1320be84cc96c5d414.css
436 ms
modernizr-2.7.1.min.js.pagespeed.jm.QFm8QPX4MP.js
326 ms
monster_jdn_atlas.js
24 ms
jquery.min.js
70 ms
plugins_c8576863332466a8c8bf734ebd9b5140.js
330 ms
site_dbe7b576c8502acfd317f93fd432d7cd.js
328 ms
main_aea36d79654a3d8df370bf838800a1de.js
646 ms
xgemius.js
635 ms
3151.jpg
347 ms
images.png
338 ms
xosc1_680x300.jpg.pagespeed.ic.ic4kwavAT8.jpg
444 ms
121x179x0229st2_121x179.jpg.pagespeed.ic.m7_jglDXuE.jpg
342 ms
96x142x0228lsrb1_96x142.jpg.pagespeed.ic.UK4LRy1hVg.jpg
341 ms
146x216x0227szig0_146x216.jpg.pagespeed.ic.jPQZcFez2a.jpg
339 ms
230x160x1025pega3_230x160.jpg.pagespeed.ic.NsEiNc8Je-.jpg
497 ms
230x160x0223intel3_230x160.jpg.pagespeed.ic.iZbBiFcIRW.jpg
659 ms
230x160x0222ora3_230x160.jpg.pagespeed.ic.FkYT8Q9CCE.jpg
662 ms
310x137x0220jwebbt2_310x137.jpg.pagespeed.ic.n2PGyuLk61.jpg
661 ms
310x137x0223vgalactic2_310x137.jpg.pagespeed.ic.U75l5ISPWe.jpg
660 ms
310x137x0224nine1_310x137.jpg.pagespeed.ic.xgfQW8cFp3.jpg
764 ms
230x340x0226cez3_230x340.jpg.pagespeed.ic.Be6Kd6-zpg.jpg
922 ms
230x160xhurok3_230x160.jpg.pagespeed.ic.Dh-vScVvQP.jpg
980 ms
230x340x0227hey0_230x340.jpg.pagespeed.ic.RqQWir-xy1.jpg
982 ms
230x160x0226mar2_230x160.jpg.pagespeed.ic.V4UOaPjI99.jpg
982 ms
nano.aspx
30 ms
adservercontinuation.aspx
171 ms
analytics.js
27 ms
all.js
417 ms
fpdata.js
146 ms
lsget.html
532 ms
adimage.aspx
29 ms
collect
18 ms
collect
7 ms
adimage.aspx
30 ms
adimage.aspx
30 ms
adimage.aspx
30 ms
adimage.aspx
20 ms
redot.gif
125 ms
47 ms
xd_arbiter.php
423 ms
rexdot.js
126 ms
like_box.php
113 ms
xd_arbiter.php
139 ms
roNeOY-tz5Y.css
288 ms
UHhaxo8Cs3k.css
356 ms
Qz9nHTUX1Wv.css
427 ms
_rx8naC75Dy.js
620 ms
x5F9OMjKyLw.js
639 ms
ICDbTSzjQEg.js
496 ms
TTCre3391I0.js
496 ms
rFmE1g6Dkoz.js
702 ms
7cm7D75Y0Sf.js
560 ms
C-h3nYPqETO.js
650 ms
oRoBXlHCpEy.js
562 ms
336JejShbZp.js
650 ms
sj-JwAJi4AH.js
696 ms
DKRU1bYTkTw.js
684 ms
ZNPAadQNc33.js
690 ms
W0OV23mIOyO.js
696 ms
36TdwhIHusi.js
697 ms
10629733_778984548827102_8109085364389799176_n.jpg
279 ms
11193246_931241100261432_1633655486303684023_n.jpg
348 ms
11904639_1114784895226214_7242492133446437945_n.jpg
417 ms
11174798_1602903429949210_3567899497941011306_n.jpg
483 ms
11062422_876417999079848_3104857896680351748_n.jpg
484 ms
12734263_1010623375676078_1281242759962341103_n.jpg
485 ms
10407902_903645763030978_3298448521350450507_n.jpg
485 ms
19229_1380395545622138_7830014953052282006_n.jpg
486 ms
wL6VQj7Ab77.png
70 ms
s7jcwEQH7Sx.png
69 ms
pUFVdPjIRct.png
69 ms
I6-MnjEovm5.js
69 ms
vlXaquuXMrr.js
70 ms
sg.hu 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.
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
<frame> or <iframe> elements do not have a title
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
sg.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
Browser errors were logged to the console
sg.hu SEO score
HU
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Sg.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 Sg.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.
sg.hu
Open Graph description is not detected on the main page of SG. 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: