5.8 sec in total
391 ms
5 sec
376 ms
Click here to check amazing EPAR content. Otherwise, check out these important facts you probably never knew about epar.nl
EPAR is an organisation for the PhD student community of the Erasmus University Rotterdam.
Visit epar.nlWe analyzed Epar.nl page load time and found that the first response time was 391 ms and then it took 5.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
epar.nl performance score
name
value
score
weighting
Value6.9 s
1/100
10%
Value7.2 s
5/100
25%
Value13.4 s
2/100
10%
Value1,690 ms
11/100
30%
Value0.432
22/100
15%
Value15.9 s
6/100
10%
391 ms
1595 ms
265 ms
279 ms
281 ms
Our browser made a total of 56 requests to load all elements on the main page. We found that 93% of them (52 requests) were addressed to the original Epar.nl, 4% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Epar.nl.
Page size can be reduced by 817.5 kB (41%)
2.0 MB
1.2 MB
In fact, the total size of Epar.nl main page is 2.0 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. 30% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 65.6 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 65.6 kB or 77% of the original size.
Potential reduce by 386.0 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, EPAR needs image optimization as it can save up to 386.0 kB or 28% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 170.9 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 170.9 kB or 63% of the original size.
Potential reduce by 195.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. Epar.nl needs all CSS files to be minified and compressed as it can save up to 195.0 kB or 78% of the original size.
Number of requests can be reduced by 20 (45%)
44
24
The browser has sent 44 CSS, Javascripts, AJAX and image requests in order to completely render the main page of EPAR. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
epar.nl
391 ms
www.epar.nl
1595 ms
wp-emoji-release.min.js
265 ms
styles.css
279 ms
default.min.css
281 ms
style.css
280 ms
fontfaces.css
289 ms
style.css
395 ms
jquery.js
510 ms
jquery-migrate.min.js
388 ms
wp-activity.css
191 ms
style-mobile.css
373 ms
dashicons.min.css
386 ms
front.css
432 ms
ajax.js
374 ms
scripts.js
374 ms
underscore.min.js
391 ms
front.min.js
571 ms
frontend.js
440 ms
nivo.slider.min.js
453 ms
validate.js
457 ms
wp-embed.min.js
466 ms
wp-activity.css
438 ms
Facebook.png
175 ms
Twitter.png
176 ms
RSS.png
177 ms
tempera.png
202 ms
EPAR-Logo-Klein.png
173 ms
Barbecue-620x410.png
554 ms
PhD-Day-1-1180x410.jpg
419 ms
Photo-shoot-736x410.jpg
321 ms
promovendis-1.png
294 ms
proefschriftmaken.png
302 ms
gildeprint-logo.png
303 ms
Optima-logo-nieuw.png
376 ms
logo-ridderprint-2016s.png
399 ms
GVO_logo_DEF.png
404 ms
Barbecue-620x350.png
705 ms
PhD-Day-1-780x350.jpg
532 ms
PNN-3.png
604 ms
Photo-shoot-736x350.jpg
575 ms
loading.gif
408 ms
dashed-border.png
500 ms
EPAR-Logo-Klein.png
846 ms
css
33 ms
ubuntu-regular-webfont.woff
464 ms
elusive.woff
501 ms
DroidSans-webfont.woff
529 ms
OpenSans-Light-webfont.woff
528 ms
yanonekaffeesatz-regular-webfont.woff
566 ms
analytics.js
33 ms
arrows.png
495 ms
hustle.ttf
498 ms
hustle.woff
518 ms
collect
11 ms
collect
51 ms
epar.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.
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.
epar.nl best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
epar.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
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Epar.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 Epar.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.
epar.nl
Open Graph description is not detected on the main page of EPAR. 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: