4.6 sec in total
750 ms
3.6 sec
227 ms
Visit ghf.dk now to see the best up-to-date G HF content for Denmark and also check out these interesting facts you probably never knew about ghf.dk
Bliv klædt godt på til fremtidig uddannelse med en 2-årig hf på Gentofte HF. Læs mere om skolen og vores spændende fagpakker her på siden.
Visit ghf.dkWe analyzed Ghf.dk page load time and found that the first response time was 750 ms and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
ghf.dk performance score
name
value
score
weighting
Value3.1 s
47/100
10%
Value8.5 s
1/100
25%
Value8.5 s
18/100
10%
Value4,730 ms
0/100
30%
Value0
100/100
15%
Value9.8 s
28/100
10%
750 ms
203 ms
208 ms
208 ms
210 ms
Our browser made a total of 82 requests to load all elements on the main page. We found that 68% of them (56 requests) were addressed to the original Ghf.dk, 17% (14 requests) were made to Scontent.xx.fbcdn.net and 12% (10 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Ghf.dk.
Page size can be reduced by 473.1 kB (8%)
5.9 MB
5.4 MB
In fact, the total size of Ghf.dk main page is 5.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. 65% of websites need less resources to load. Images take 5.6 MB which makes up the majority of the site volume.
Potential reduce by 27.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 27.4 kB or 80% of the original size.
Potential reduce by 239.2 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. G HF images are well optimized though.
Potential reduce by 131.8 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 131.8 kB or 67% of the original size.
Potential reduce by 74.8 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. Ghf.dk needs all CSS files to be minified and compressed as it can save up to 74.8 kB or 83% of the original size.
Number of requests can be reduced by 26 (34%)
77
51
The browser has sent 77 CSS, Javascripts, AJAX and image requests in order to completely render the main page of G HF. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
ghf.dk
750 ms
jquery.jscrollpane.min.css
203 ms
customcolors.css
208 ms
cardozafacebook.css
208 ms
mappress.css
210 ms
style.css
207 ms
ghf.pix.min.css
274 ms
css
27 ms
jquery.js
508 ms
jquery-migrate.min.js
306 ms
jquery.lightbox.min.js
311 ms
jquery.lightbox.plugin.min.js
309 ms
jquery.jscrollpane.min.js
308 ms
wpjsp.js
371 ms
cardozafacebook.js
407 ms
soliloquy.css
244 ms
jquery-ui-1.10.4.custom.min.js
249 ms
ghf.pix.min.js
247 ms
navigation.js
310 ms
soliloquy.js
343 ms
style.css
314 ms
hgroup-bg.png
204 ms
logo.png
103 ms
belfast-11-2-980x500_t.jpg
1505 ms
holder.gif
106 ms
preloader.gif
583 ms
bullet_odd.png
107 ms
bullet_even.png
208 ms
meddelelser_arrow_up.png
989 ms
meddelelser_arrow_down.png
981 ms
122.jpg
841 ms
IMG_0319-b.jpg
644 ms
IMG_2788.jpg
1101 ms
BebasNeue.otf
726 ms
jquery.lightbox.min.css
824 ms
likebox.php
140 ms
loading.gif
870 ms
prev.gif
884 ms
next.gif
969 ms
blank.gif
985 ms
belfast-5-b-980x500_t.jpg
1726 ms
belfast-8-b-980x500_t.jpg
1736 ms
belfast-6-b-980x500_t.jpg
1467 ms
IMG_2116-b-980x500_t.jpg
1386 ms
IMG_1907-b-980x500_t.jpg
1646 ms
IMG_2032-b-980x500_t.jpg
1789 ms
IMG_2054-b-980x500_t.jpg
1942 ms
IMG_2095-b-980x500_t.jpg
1870 ms
IMG_2106-b-980x500_t.jpg
1954 ms
IMG_2196-b-980x500_t.jpg
2237 ms
IMG_2222-b-980x500_t.jpg
2150 ms
IMG_2244-b-980x500_t.jpg
2090 ms
IMG_2238-b-980x500_t.jpg
2270 ms
IMG_2266-b-980x500_t.jpg
2351 ms
IMG_2283-b-980x500_t.jpg
2380 ms
slider-dots.png
2193 ms
meddelelser_arrow_up.png
2257 ms
meddelelser_arrow_down.png
2293 ms
ebiMDO3r-8l.css
49 ms
jGc-59L_9lo.css
41 ms
q68gy-v_YMF.js
51 ms
FJmpeSpHpjS.js
49 ms
0wM5s1Khldu.js
49 ms
1bNoFZUdlYZ.js
46 ms
12650830_939491439466379_6091709783564592149_n.jpg
43 ms
942850_942698152479041_3540756959454278968_n.png
15 ms
12376004_10207283466058479_4452619056579411263_n.jpg
11 ms
11693921_10153819861782340_4139210886501982172_n.jpg
12 ms
1382175_10205312008584657_4479344682329283189_n.jpg
14 ms
10416609_10203503192233641_8310899914208892038_n.jpg
13 ms
1383981_139069186481534_3170858509493477511_n.jpg
31 ms
541687_10201006718043238_1310273019_n.jpg
78 ms
12813924_10209142047934392_2794600739577558080_n.jpg
55 ms
10931378_10204727592242566_9218921806818366655_n.jpg
14 ms
10403580_10202633862587788_9110914457313667793_n.jpg
79 ms
12645207_10153449784325028_6263102861724058356_n.jpg
15 ms
60811_159119054114416_1009988_n.jpg
15 ms
11898537_10205898613522649_4068240545804629423_n.jpg
15 ms
wL6VQj7Ab77.png
9 ms
s7jcwEQH7Sx.png
8 ms
I6-MnjEovm5.js
3 ms
pQrUxxo5oQp.js
4 ms
ghf.dk accessibility score
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
Buttons do not have an accessible name
Form elements do not have associated labels
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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.
ghf.dk 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
Page has valid source maps
ghf.dk SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
DA
DA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ghf.dk can be misinterpreted by Google and other search engines. Our service has detected that Danish is used on the page, and it matches the claimed language. Our system also found out that Ghf.dk 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.
ghf.dk
Open Graph description is not detected on the main page of G HF. 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: