Tools & Wizards About Us
aepos.nl screenshot

Report Summary

  • 63

    Performance

    Renders faster than
    77% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

aepos.nl

Aepos Opleiding & advies, werving & selectie, coaching en loopbaanadvisering Friesland

Page Load Speed

3.3 sec in total

First Response

486 ms

Resources Loaded

2.7 sec

Page Rendered

159 ms

aepos.nl screenshot

About Website

Click here to check amazing Aepos content. Otherwise, check out these important facts you probably never knew about aepos.nl

Visit aepos.nl

Key Findings

We analyzed Aepos.nl page load time and found that the first response time was 486 ms and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

aepos.nl performance score

63

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

34/100

10%

LCP (Largest Contentful Paint)

Value6.1 s

12/100

25%

SI (Speed Index)

Value4.5 s

73/100

10%

TBT (Total Blocking Time)

Value180 ms

91/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value5.9 s

65/100

10%

Network Requests Diagram

aepos.nl

486 ms

wp-emoji-release.min.js

200 ms

style.min.css

309 ms

classic-themes.min.css

294 ms

style.min.css

281 ms

Our browser made a total of 58 requests to load all elements on the main page. We found that 78% of them (45 requests) were addressed to the original Aepos.nl, 21% (12 requests) were made to Fonts.gstatic.com and 2% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (784 ms) belongs to the original domain Aepos.nl.

Page Optimization Overview & Recommendations

Page size can be reduced by 97.1 kB (47%)

Content Size

205.5 kB

After Optimization

108.4 kB

  • HTML
  • Images

In fact, the total size of Aepos.nl main page is 205.5 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 55% of websites need less resources to load. HTML takes 122.6 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 94.8 kB

  • Original 122.6 kB
  • After minification 121.2 kB
  • After compression 27.8 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 94.8 kB or 77% of the original size.

Image Optimization

-3%

Potential reduce by 2.4 kB

  • Original 83.0 kB
  • After minification 80.6 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. Aepos images are well optimized though.

Requests Breakdown

Number of requests can be reduced by 40 (89%)

Requests Now

45

After Optimization

5

  • Images
  • JavaScript
  • CSS

The browser has sent 45 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Aepos. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 23 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

aepos.nl

aepos.nl

486 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

200 ms

style.min.css

style.min.css

309 ms

classic-themes.min.css

classic-themes.min.css

294 ms

style.min.css

style.min.css

281 ms

theme.min.css

theme.min.css

294 ms

frontend.min.css

frontend.min.css

302 ms

elementor-icons.min.css

elementor-icons.min.css

319 ms

frontend-lite.min.css

frontend-lite.min.css

385 ms

swiper.min.css

swiper.min.css

387 ms

post-4622.css

post-4622.css

389 ms

frontend-lite.min.css

frontend-lite.min.css

418 ms

global.css

global.css

414 ms

post-4634.css

post-4634.css

412 ms

post-4661.css

post-4661.css

475 ms

style.min.css

style.min.css

501 ms

font-awesome.min.css

font-awesome.min.css

498 ms

post-4678.css

post-4678.css

503 ms

css

css

32 ms

fontawesome.min.css

fontawesome.min.css

514 ms

solid.min.css

solid.min.css

519 ms

jquery.min.js

jquery.min.js

695 ms

jquery-migrate.min.js

jquery-migrate.min.js

609 ms

widget-nav-menu.min.css

widget-nav-menu.min.css

599 ms

widget-icon-box.min.css

widget-icon-box.min.css

607 ms

post-4674.css

post-4674.css

553 ms

animations.min.css

animations.min.css

559 ms

happy-addons.min.js

happy-addons.min.js

678 ms

happy-addons-pro.js

happy-addons-pro.js

681 ms

jquery.smartmenus.min.js

jquery.smartmenus.min.js

682 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

678 ms

webpack.runtime.min.js

webpack.runtime.min.js

679 ms

frontend-modules.min.js

frontend-modules.min.js

739 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

752 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

752 ms

wp-polyfill.min.js

wp-polyfill.min.js

784 ms

hooks.min.js

hooks.min.js

761 ms

i18n.min.js

i18n.min.js

784 ms

frontend.min.js

frontend.min.js

708 ms

waypoints.min.js

waypoints.min.js

635 ms

core.min.js

core.min.js

633 ms

frontend.min.js

frontend.min.js

638 ms

elements-handlers.min.js

elements-handlers.min.js

647 ms

circle.svg

circle.svg

214 ms

aepos-logo-transparant-300x110.png

aepos-logo-transparant-300x110.png

203 ms

20140909-186.jpg

20140909-186.jpg

305 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

23 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

30 ms

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

45 ms

KFOkCnqEu92Fr1MmgVxIIzc.ttf

KFOkCnqEu92Fr1MmgVxIIzc.ttf

62 ms

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

64 ms

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

64 ms

KFOkCnqEu92Fr1Mu51xIIzc.ttf

KFOkCnqEu92Fr1Mu51xIIzc.ttf

62 ms

KFOjCnqEu92Fr1Mu51S7ACc6CsE.ttf

KFOjCnqEu92Fr1Mu51S7ACc6CsE.ttf

64 ms

KFOjCnqEu92Fr1Mu51TjASc6CsE.ttf

KFOjCnqEu92Fr1Mu51TjASc6CsE.ttf

61 ms

KFOiCnqEu92Fr1Mu51QrEzAdKg.ttf

KFOiCnqEu92Fr1Mu51QrEzAdKg.ttf

67 ms

KFOjCnqEu92Fr1Mu51TzBic6CsE.ttf

KFOjCnqEu92Fr1Mu51TzBic6CsE.ttf

65 ms

KFOjCnqEu92Fr1Mu51TLBCc6CsE.ttf

KFOjCnqEu92Fr1Mu51TLBCc6CsE.ttf

66 ms

Accessibility Review

aepos.nl accessibility score

93

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

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

High

Links do not have a discernible name

Best Practices

aepos.nl best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

aepos.nl SEO score

93

Search Engine Optimization Advices

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    NL

  • Language Claimed

    NL

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Aepos.nl can be misinterpreted by Google and other search engines. Our service has detected that Dutch is used on the page, and it matches the claimed language. Our system also found out that Aepos.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.

Social Sharing Optimization

aepos.nl

Open Graph description is not detected on the main page of Aepos. 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: