7.4 sec in total
347 ms
6.8 sec
214 ms
Welcome to iqb.de homepage info - get ready to check IQB best content for Germany right away, or after learning these important things about iqb.de
Karrieremessen im Hochschulumfeld - Akademischen Nachwuchs trifft Arbeitgeber: Einfach, unkompliziert und auf Augenhöhe.
Visit iqb.deWe analyzed Iqb.de page load time and found that the first response time was 347 ms and then it took 7 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
iqb.de performance score
name
value
score
weighting
Value4.3 s
18/100
10%
Value8.6 s
1/100
25%
Value6.0 s
46/100
10%
Value1,130 ms
22/100
30%
Value0.017
100/100
15%
Value10.3 s
24/100
10%
347 ms
756 ms
244 ms
248 ms
896 ms
Our browser made a total of 162 requests to load all elements on the main page. We found that 94% of them (153 requests) were addressed to the original Iqb.de, 1% (2 requests) were made to Google-code-prettify.googlecode.com and 1% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Iqb.de.
Page size can be reduced by 1.1 MB (57%)
1.8 MB
780.3 kB
In fact, the total size of Iqb.de 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. 40% of websites need less resources to load. Javascripts take 787.3 kB which makes up the majority of the site volume.
Potential reduce by 60.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. This page needs HTML code to be minified as it can gain 13.0 kB, which is 18% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 60.7 kB or 82% of the original size.
Potential reduce by 53.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. Obviously, IQB needs image optimization as it can save up to 53.9 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 528.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 528.8 kB or 67% of the original size.
Potential reduce by 406.7 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. Iqb.de needs all CSS files to be minified and compressed as it can save up to 406.7 kB or 84% of the original size.
Number of requests can be reduced by 120 (75%)
160
40
The browser has sent 160 CSS, Javascripts, AJAX and image requests in order to completely render the main page of IQB. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and from 96 to 1 for CSS and as a result speed up the page load time.
iqb.de
347 ms
www.iqb.de
756 ms
main.css
244 ms
main.css
248 ms
barebone.jsp
896 ms
main.css
246 ms
font-awesome.css
252 ms
font-icomoon.css
358 ms
jquery.fancybox-1.3.4.css
366 ms
prettify.css
369 ms
camera.css
370 ms
js
27 ms
superfish.js
375 ms
gmaps.js
487 ms
jquery.colorbox-min.js
488 ms
masonry.pkgd.min.js
614 ms
jquery.dataTables.min.js
743 ms
main.css
267 ms
main.js
376 ms
jquery.fancybox-1.3.4.pack.js
377 ms
filterable.pack.min.js
390 ms
jquery.fitvids.min.js
498 ms
jquery.flexslider-min.js
501 ms
jquery.tweet.js
506 ms
jquery.easing-1.3.pack.js
513 ms
camera.min.js
624 ms
jquery.mobile.customized.min.js
624 ms
run_prettify.js
89 ms
aui.css
753 ms
portal_1.css
626 ms
portal_2.css
631 ms
taglib_1.css
741 ms
taglib_2.css
743 ms
openid.css
747 ms
accessibility.css
757 ms
generic_portal.css
152 ms
add_content.css
240 ms
flyout.css
241 ms
panel_component.css
247 ms
panel_pagination.css
251 ms
position_helper.css
253 ms
auto_row.css
275 ms
undo_manager.css
361 ms
panel_page.css
363 ms
javascript_template.css
368 ms
portlet_item.css
375 ms
portlet_css_editor.css
375 ms
portlet_toolbar.css
398 ms
toolbar.css
484 ms
tree.css
484 ms
uploader.css
489 ms
page_settings.css
495 ms
notifications.css
496 ms
asset_category_selector.css
518 ms
asset_column.css
605 ms
tag_selector.css
604 ms
generic_portlet.css
609 ms
forms.css
617 ms
header_row.css
619 ms
preview.css
642 ms
rich_editor.css
726 ms
search_combobox.css
727 ms
separator.css
730 ms
top_links.css
740 ms
translation_manager.css
741 ms
asset_categories_summary.css
658 ms
asset_links.css
740 ms
calendar.css
741 ms
captcha.css
740 ms
categorization_filter.css
740 ms
diff.css
743 ms
diff_html.css
746 ms
discussion.css
739 ms
flags.css
739 ms
form_navigator.css
736 ms
header.css
744 ms
icon.css
745 ms
icon_help.css
746 ms
icon_list.css
739 ms
icon_menu.css
739 ms
input_localized.css
736 ms
input_move_boxes.css
742 ms
input_repeat.css
745 ms
language.css
746 ms
logo_selector.css
739 ms
preview.css
739 ms
ratings.css
737 ms
search_iterator.css
744 ms
search_toggle.css
745 ms
social_activities.css
746 ms
social_bookmarks.css
738 ms
tags_summary.css
737 ms
user_display.css
737 ms
webdav.css
745 ms
workflow_status.css
745 ms
ga.js
26 ms
base.css
124 ms
application.css
125 ms
layout.css
130 ms
dockbar.css
133 ms
navigation.css
127 ms
portlet.css
127 ms
forms.css
244 ms
extras.css
246 ms
custom.css
501 ms
__utm.gif
25 ms
css
26 ms
font-icomoon.css
126 ms
colorbox.css
125 ms
gray.css
128 ms
green.css
126 ms
teal.css
129 ms
orange.css
126 ms
purple.css
245 ms
jquery.min.js
372 ms
127 ms
webfont.js
36 ms
logo.png
181 ms
82ec5854-f45c-453c-9fbd-413608d3af00
400 ms
92a2a19c-c62e-4d8d-8ab8-54c97a8081ec
279 ms
34a60219-ac9c-4f46-9ab7-56195c494f17
278 ms
3eec02f9-7d89-4917-a4f5-418d76cecb93
524 ms
9b018648-d525-4eeb-9d73-4dc616ab4c1e
525 ms
1ed97c27-cf2b-412f-9f48-8d0271f9baa8
383 ms
17af5451-b206-4628-91d2-5e3d27e35380
425 ms
f7b0747b-d4ec-4056-9a92-17983f79aa86
426 ms
837c0a94-37dc-404e-bb0c-818d128c62dd
521 ms
46cc25f5-caa4-4820-b171-843444e95c3b
536 ms
96982b02-2103-47ed-bec9-444cd70f6c8e
571 ms
b656c67e-4610-4038-8c77-82a1e1bfb868
567 ms
aea8d35b-14d6-4395-9fc1-830382462a10
663 ms
1a6a87ca-9ff9-48fa-8fc5-4cb82bcc1a15
665 ms
42b97afa-c8af-4305-af6b-b5ce949f7403
667 ms
c84b817c-5191-4e0c-9ad3-e3e3a0b6abd6
674 ms
be557dbf-4f76-4c16-88d1-27b9b41ed9e4
706 ms
d9ed6dd2-9486-487c-bf0e-dece790212b4
712 ms
66649ca6-337c-4156-93e2-d41720e283b3
804 ms
ab1ae62f-5aec-427d-a317-b292884da300
804 ms
9a03aad1-a4cc-4dd3-918a-ab3d1d83b00b
814 ms
bdf7e91f-c781-4a50-8493-c63c49ca223d
814 ms
08c6a67e-3c96-4da8-9799-bca6ad96d0d6
848 ms
ff1b46ce-b875-413a-9b73-095a9578ed58
852 ms
fa8899be-1c6d-4505-8236-1057b712b0f3
945 ms
6fc51841-f556-46b3-b9c7-d545a3f59524
954 ms
7eea1fd6-a6a9-413b-907e-3f876cfbfc77
953 ms
41671155-1e1d-4a03-be5e-11a976c99bc0
955 ms
95f799e3-55de-480c-9a40-64c7e675a484
986 ms
add_user.png
974 ms
help.png
1066 ms
css
14 ms
top-shadow.png
1018 ms
piwik.js
644 ms
prettify.css
69 ms
camera-loader.gif
903 ms
overlay.png
902 ms
bbd84d0b-7d50-4089-ac78-c0e864749b49
1306 ms
logo_xing_white.png
926 ms
logo_fb_white.png
916 ms
noise_bg.png
923 ms
icn_on.png
539 ms
icn_off.png
124 ms
d16a2d24-7e9e-48c0-ae84-6e05a3ab93b1
862 ms
iqb.de accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[role]s do not have all required [aria-*] attributes
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
Image elements do not have [alt] attributes
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
iqb.de best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
iqb.de SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
DE
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Iqb.de can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it matches the claimed language. Our system also found out that Iqb.de 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.
iqb.de
Open Graph description is not detected on the main page of IQB. 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: