Report Summary

  • 62

    Performance

    Renders faster than
    76% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 88% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

apenheul.com

Apenheul, a zoo of free-roaming primates! - Apenheul

Page Load Speed

3.2 sec in total

First Response

830 ms

Resources Loaded

2.1 sec

Page Rendered

331 ms

apenheul.com screenshot

About Website

Welcome to apenheul.com homepage info - get ready to check Apenheul best content right away, or after learning these important things about apenheul.com

A forest full of primates roaming freely, that’s what Apenheul is all about! In this zoo more than half of the primates roam freely among the visitors

Visit apenheul.com

Key Findings

We analyzed Apenheul.com page load time and found that the first response time was 830 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

apenheul.com performance score

62

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

56/100

10%

LCP (Largest Contentful Paint)

Value2.9 s

80/100

25%

SI (Speed Index)

Value5.1 s

61/100

10%

TBT (Total Blocking Time)

Value680 ms

44/100

30%

CLS (Cumulative Layout Shift)

Value0.069

96/100

15%

TTI (Time to Interactive)

Value10.3 s

24/100

10%

Network Requests Diagram

apenheul.com

830 ms

gtm.js

130 ms

css.css

168 ms

style.css

117 ms

lib.bundle.js

626 ms

Our browser made a total of 30 requests to load all elements on the main page. We found that 87% of them (26 requests) were addressed to the original Apenheul.com, 7% (2 requests) were made to Cdn.icomoon.io and 3% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (830 ms) belongs to the original domain Apenheul.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 160.7 kB (15%)

Content Size

1.0 MB

After Optimization

876.5 kB

In fact, the total size of Apenheul.com main page is 1.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. 35% of websites need less resources to load. Javascripts take 527.8 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 40.1 kB

  • Original 53.3 kB
  • After minification 43.2 kB
  • After compression 13.1 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. This page needs HTML code to be minified as it can gain 10.0 kB, which is 19% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 40.1 kB or 75% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 392.7 kB
  • After minification 392.7 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. Apenheul images are well optimized though.

JavaScript Optimization

-23%

Potential reduce by 119.7 kB

  • Original 527.8 kB
  • After minification 527.8 kB
  • After compression 408.1 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 119.7 kB or 23% of the original size.

CSS Optimization

-1%

Potential reduce by 871 B

  • Original 63.5 kB
  • After minification 63.5 kB
  • After compression 62.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. Apenheul.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 3 (12%)

Requests Now

25

After Optimization

22

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

Accessibility Review

apenheul.com accessibility score

96

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

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

High

Links do not have a discernible name

Best Practices

apenheul.com 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

High

Missing source maps for large first-party JavaScript

SEO Factors

apenheul.com SEO score

92

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Apenheul.com 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 Apenheul.com 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

Open Graph data is detected on the main page of Apenheul. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: