1.6 sec in total
118 ms
1.4 sec
149 ms
Welcome to questionmark.eu homepage info - get ready to check Questionmark best content for South Africa right away, or after learning these important things about questionmark.eu
Visit questionmark.euWe analyzed Questionmark.eu page load time and found that the first response time was 118 ms and then it took 1.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.
questionmark.eu performance score
name
value
score
weighting
Value6.1 s
3/100
10%
Value6.5 s
9/100
25%
Value9.7 s
10/100
10%
Value1,000 ms
27/100
30%
Value0.026
100/100
15%
Value22.6 s
1/100
10%
118 ms
75 ms
182 ms
33 ms
34 ms
Our browser made a total of 81 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Questionmark.eu, 79% (64 requests) were made to Questionmark.com and 5% (4 requests) were made to F.vimeocdn.com. The less responsive or slowest element that took the longest time to load (674 ms) relates to the external source Questionmark.com.
Page size can be reduced by 1.1 MB (75%)
1.4 MB
358.7 kB
In fact, the total size of Questionmark.eu main page is 1.4 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 907.3 kB 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 77% of the original size.
Potential reduce by 5.8 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, Questionmark needs image optimization as it can save up to 5.8 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 663.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 663.3 kB or 73% of the original size.
Potential reduce by 360.6 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. Questionmark.eu needs all CSS files to be minified and compressed as it can save up to 360.6 kB or 86% of the original size.
Number of requests can be reduced by 52 (69%)
75
23
The browser has sent 75 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Questionmark. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 32 to 1 for JavaScripts and from 22 to 1 for CSS and as a result speed up the page load time.
questionmark.eu
118 ms
questionmark.eu
75 ms
www.questionmark.com
182 ms
system.base.css
33 ms
date.css
34 ms
datepicker.1.7.css
36 ms
field.css
45 ms
i18n_menu_overview.css
45 ms
node.css
89 ms
webform_feedback.css
63 ms
youtube.css
65 ms
views.css
63 ms
apachesolr_autocomplete.css
63 ms
jquery.autocomplete.css
64 ms
ctools.css
65 ms
jquerymenu.css
73 ms
panels.css
71 ms
book_made_simple.css
69 ms
honeypot.css
68 ms
webform.css
79 ms
node_embed.css
79 ms
lang_dropdown.css
76 ms
style.css
308 ms
css
87 ms
logo.png
71 ms
q.png
75 ms
78358751
102 ms
feed
98 ms
jquery.min.js
66 ms
jquery-migrate.min.js
65 ms
jquery.once.js
68 ms
drupal.js
67 ms
jquery.cookie.js
70 ms
authcache.js
70 ms
apachesolr_autocomplete.js
70 ms
jquery.autocomplete.js
286 ms
jquerymenu.js
75 ms
textarea.js
71 ms
questionmark_search.js
71 ms
webform.js
284 ms
webform_feedback.js
166 ms
googleanalytics.js
281 ms
lang_dropdown.js
194 ms
jquery.ba-postmessage.js
279 ms
bootstrap.js
471 ms
jquery.plugin.js
406 ms
jquery.countdown.js
429 ms
jquery.fancybox.pack.js
404 ms
jquery.fancybox-buttons.js
359 ms
jquery.fancybox-media.js
383 ms
jquery.fancybox-thumbs.js
382 ms
ua-parser.min.js
477 ms
app.js
674 ms
html5gallery.js
380 ms
homepage-01-authoring_140x80-v2.png
591 ms
homepage-02-delivery_140x80-v2.png
451 ms
homepage-03-reporting_140x80-v2.png
460 ms
online-proctor-100x100.png
524 ms
miami-palms-pink-100x100.png
593 ms
player.js
116 ms
player.css
89 ms
ga.js
42 ms
vuid.min.js
86 ms
__utm.gif
30 ms
proxy.html
150 ms
buzzboost-pwrd.gif
96 ms
step.png
248 ms
sap-partner-logo-120x82.gif
250 ms
ms-gold-2013-isv-app-dev.gif
477 ms
GSA-Contract-Holder-logo-233x75.png
357 ms
hropen_memberlogo136x82.png
306 ms
imscertifiedsm.gif
443 ms
analytics.js
43 ms
s-BiyweUPV0v-yRb-cjciBsxEYwM7FgeyaSgU71cLG0.woff
33 ms
glyphicons-halflings-regular.woff
361 ms
fontawesome-webfont.woff
368 ms
collect
19 ms
545962069.jpg
111 ms
throbber.gif
13 ms
feedback-tab.png
13 ms
pd.js
194 ms
questionmark.eu 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
[aria-*] attributes do not match their roles
ARIA IDs are not unique
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
Image elements do not have [alt] attributes
Links do not have a discernible name
questionmark.eu 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
Page has valid source maps
questionmark.eu SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Questionmark.eu can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Questionmark.eu 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.
questionmark.eu
Open Graph description is not detected on the main page of Questionmark. 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: