3.8 sec in total
58 ms
2.6 sec
1.1 sec
Visit eyequestion.nl now to see the best up-to-date Eye Question content and also check out these interesting facts you probably never knew about eyequestion.nl
EyeQuestion is unique software for Sensory and Consumer Research that moves you forward and drives innovation.
Visit eyequestion.nlWe analyzed Eyequestion.nl page load time and found that the first response time was 58 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 65% of websites can load faster.
eyequestion.nl performance score
name
value
score
weighting
Value6.5 s
2/100
10%
Value11.0 s
0/100
25%
Value11.4 s
5/100
10%
Value300 ms
78/100
30%
Value0
100/100
15%
Value24.0 s
1/100
10%
58 ms
78 ms
30 ms
132 ms
289 ms
Our browser made a total of 96 requests to load all elements on the main page. We found that 78% of them (75 requests) were addressed to the original Eyequestion.nl, 14% (13 requests) were made to Use.typekit.net and 2% (2 requests) were made to Salesiq.zohopublic.eu. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Eyequestion.nl.
Page size can be reduced by 130.9 kB (10%)
1.3 MB
1.2 MB
In fact, the total size of Eyequestion.nl main page is 1.3 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. 60% of websites need less resources to load. Images take 960.2 kB which makes up the majority of the site volume.
Potential reduce by 126.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 126.4 kB or 81% of the original size.
Potential reduce by 268 B
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. Eye Question images are well optimized though.
Potential reduce by 178 B
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. This website has mostly compressed JavaScripts.
Potential reduce by 4.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. Eyequestion.nl has all CSS files already compressed.
Number of requests can be reduced by 45 (58%)
78
33
The browser has sent 78 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Eye Question. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and from 25 to 1 for CSS and as a result speed up the page load time.
eyequestion.nl
58 ms
eyequestion.nl
78 ms
polyfill.min.js
30 ms
ewj2wop.css
132 ms
theme.min.css
289 ms
style.css
298 ms
custom.css
291 ms
style.min.css
298 ms
elementor-icons.min.css
300 ms
frontend-lite.min.css
375 ms
swiper.min.css
560 ms
post-7.css
557 ms
frontend-lite.min.css
567 ms
post-13.css
594 ms
post-10159.css
572 ms
post-10201.css
645 ms
fontawesome.min.css
898 ms
solid.min.css
832 ms
brands.min.css
831 ms
jquery.min.js
587 ms
jquery-migrate.min.js
605 ms
widget-nav-menu.min.css
860 ms
widget-theme-elements.min.css
882 ms
widget-flip-box.min.css
985 ms
widget-posts.min.css
1107 ms
widget-carousel.min.css
1115 ms
widget-icon-list.min.css
986 ms
animations.min.css
1157 ms
extras.js
981 ms
jquery.smartmenus.min.js
983 ms
imagesloaded.min.js
983 ms
webpack-pro.runtime.min.js
982 ms
webpack.runtime.min.js
983 ms
frontend-modules.min.js
984 ms
wp-polyfill-inert.min.js
983 ms
regenerator-runtime.min.js
985 ms
wp-polyfill.min.js
985 ms
hooks.min.js
986 ms
i18n.min.js
988 ms
frontend.min.js
988 ms
gtm.js
59 ms
p.css
20 ms
waypoints.min.js
707 ms
core.min.js
715 ms
frontend.min.js
708 ms
elements-handlers.min.js
724 ms
jquery.sticky.min.js
722 ms
logo-eyequestion.png
350 ms
hero-culry-girl-scaled.jpg
356 ms
hero-arrow.png
346 ms
video-overlay-circles.svg
448 ms
Tasting-Coffee-767x431.jpg
457 ms
IMG_4055-300x200.jpg
508 ms
black-landscape-nexus-7-held-by-a-woman-300x225.png
611 ms
Eyequestion-VR-tasting-300x169.png
626 ms
heineken-nv-vector-logo.png
628 ms
heintz_logo-1024x420.png
722 ms
Pepsico_logo-1024x294.png
472 ms
nestle-logo-black-and-white-1024x355.png
740 ms
BDF_Logo_negativeWhite-1024x377.jpg
790 ms
danone_logo-1024x576.png
834 ms
Puratos_logo.png
931 ms
wendy_logo-1024x340.png
857 ms
wageningen_logo.png
971 ms
kerry_logo2.png
987 ms
Philips-logo.png
773 ms
fc_logo.png
1067 ms
438px-Logo_Jacobs_Douwe_Egberts.svg.png
1182 ms
1200px-Dr._Oetker-Logo.svg-1024x652.png
1125 ms
880px-Cargill_logo.svg.png
1208 ms
TheHersheyCompany_VIS_Logo_pos_PMS_NoCopy__5_28_2020.5ecfd74b9da2c-1024x433.png
1292 ms
2018_PGlogo-300x300-1.png
1253 ms
d
4 ms
d
11 ms
d
16 ms
d
17 ms
d
17 ms
d
17 ms
fa-solid-900.woff
1358 ms
d
15 ms
d
25 ms
d
25 ms
d
27 ms
d
26 ms
d
26 ms
Unilever_logo-e1597757492716.png
1395 ms
drink-production-employee-works-food-beverage-manufacturing-quality-check-ing-production-line_small-300x200.jpg
1197 ms
Blog-image-Version-6-300x157.png
1469 ms
Picture1-300x257.jpg
1476 ms
eq-logo-white-2.png
1509 ms
widget
574 ms
fa-brands-400.woff
1249 ms
website
116 ms
floatbutton1_0uA5KIDjSJBNGPeiRDI3YtNcjWJ9mZsPq48NM5iMzp7_jWYVkIHbMtgrDX_xil60_.css
99 ms
floatbutton1_OMB1lZpjBxrwTfWk7tu-agd4LITXl_Zfgf3EAtKwKNAjawpq49QmYXGByYNmBoIV_.js
132 ms
siq_mpWsf52LIPg9mU40fjRdjF6WMUs-Q0VNu4KH07GkhNZGQTRxW2eRyFJLAq9VKCYB_.ttf
22 ms
eyequestion.nl 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.
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 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
Links do not have a discernible name
eyequestion.nl 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
eyequestion.nl 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
EN
NL
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Eyequestion.nl can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Dutch language. Our system also found out that Eyequestion.nl 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.
eyequestion.nl
Open Graph data is detected on the main page of Eye Question. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: