6.2 sec in total
95 ms
4.1 sec
2 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 95 ms and then it took 6.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
eyequestion.nl performance score
name
value
score
weighting
Value7.9 s
0/100
10%
Value13.1 s
0/100
25%
Value18.2 s
0/100
10%
Value11,310 ms
0/100
30%
Value0.139
79/100
15%
Value24.9 s
0/100
10%
95 ms
84 ms
272 ms
406 ms
317 ms
Our browser made a total of 102 requests to load all elements on the main page. We found that 70% of them (71 requests) were addressed to the original Eyequestion.nl, 13% (13 requests) were made to Use.typekit.net and 2% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Eyequestion.nl.
Page size can be reduced by 140.9 kB (10%)
1.4 MB
1.3 MB
In fact, the total size of Eyequestion.nl 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.0 MB which makes up the majority of the site volume.
Potential reduce by 118.9 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 118.9 kB or 81% of the original size.
Potential reduce by 20.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. Eye Question images are well optimized though.
Potential reduce by 402 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 802 B
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 50 (60%)
84
34
The browser has sent 84 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 32 to 1 for JavaScripts and from 20 to 1 for CSS and as a result speed up the page load time.
eyequestion.nl
95 ms
polyfill.min.js
84 ms
ewj2wop.css
272 ms
style.min.css
406 ms
theme.min.css
317 ms
style.css
342 ms
custom.css
346 ms
style.min.css
343 ms
elementor-icons.min.css
349 ms
frontend-legacy.min.css
772 ms
frontend.min.css
791 ms
post-7.css
789 ms
frontend.min.css
722 ms
post-13.css
773 ms
post-10159.css
769 ms
post-10201.css
991 ms
fontawesome.min.css
1055 ms
solid.min.css
985 ms
brands.min.css
993 ms
jquery.min.js
994 ms
jquery-migrate.min.js
997 ms
animations.min.css
1797 ms
extras.js
1795 ms
jquery.smartmenus.min.js
1809 ms
imagesloaded.min.js
1782 ms
webpack-pro.runtime.min.js
1795 ms
webpack.runtime.min.js
1810 ms
frontend-modules.min.js
1813 ms
regenerator-runtime.min.js
1816 ms
wp-polyfill.min.js
1817 ms
hooks.min.js
1818 ms
i18n.min.js
1819 ms
frontend.min.js
1821 ms
waypoints.min.js
1832 ms
core.min.js
1852 ms
swiper.min.js
1873 ms
share-link.min.js
1836 ms
dialog.min.js
1873 ms
frontend.min.js
2056 ms
gtm.js
238 ms
p.css
83 ms
preloaded-elements-handlers.min.js
1819 ms
preloaded-modules.min.js
1735 ms
jquery.sticky.min.js
1789 ms
wp-emoji-release.min.js
1927 ms
analytics.js
242 ms
insight.min.js
368 ms
conversion_async.js
367 ms
js
93 ms
collect
107 ms
19 ms
68 ms
55 ms
video-overlay-circles.svg
627 ms
logo-eyequestion.png
985 ms
hero-culry-girl-scaled.jpg
1106 ms
hero-arrow.png
1120 ms
video-image-767x493.jpg
1308 ms
IMG_4055-300x200.jpg
1120 ms
black-landscape-nexus-7-held-by-a-woman-300x225.png
1219 ms
Eyequestion-VR-tasting-300x169.png
1309 ms
heineken-nv-vector-logo.png
1306 ms
heintz_logo-1024x420.png
1321 ms
Pepsico_logo-1024x294.png
1346 ms
nestle-logo-black-and-white-1024x355.png
1398 ms
BDF_Logo_negativeWhite-1024x377.jpg
1565 ms
danone_logo-1024x576.png
1511 ms
Puratos_logo.png
1224 ms
wendy_logo-1024x340.png
1095 ms
wageningen_logo.png
1210 ms
kerry_logo2.png
1222 ms
Philips-logo.png
1362 ms
fc_logo.png
1363 ms
438px-Logo_Jacobs_Douwe_Egberts.svg.png
1377 ms
1200px-Dr._Oetker-Logo.svg-1024x652.png
1520 ms
880px-Cargill_logo.svg.png
1354 ms
TheHersheyCompany_VIS_Logo_pos_PMS_NoCopy__5_28_2020.5ecfd74b9da2c-1024x433.png
1515 ms
2018_PGlogo-300x300-1.png
1548 ms
Unilever_logo-e1597757492716.png
1641 ms
Taste-of-change-300x117.jpg
1597 ms
photo5240466035562363475-1-225x300.jpg
1702 ms
widget
664 ms
d
140 ms
d
273 ms
d
272 ms
d
353 ms
d
415 ms
d
413 ms
fa-solid-900.woff
1988 ms
d
413 ms
d
544 ms
d
555 ms
d
536 ms
d
553 ms
d
553 ms
fa-brands-400.woff
1731 ms
eq-logo-white-2.png
1849 ms
website
114 ms
floatbutton1_764bf172fd710d0d540b777a5a05ab02_.css
181 ms
floatbutton1_ee71224b7a4031c47ac08e0c631591de_.js
170 ms
float_6cd76475d822e7b44efcf2b1413f4967_.ttf
35 ms
32 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.
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
eyequestion.nl 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
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 Eyequestion.nl 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 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: