Report Summary

  • 31

    Performance

    Renders faster than
    51% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 87% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

epla.aha.io

Log in to your workspace | Aha!

Page Load Speed

672 ms in total

First Response

17 ms

Resources Loaded

577 ms

Page Rendered

78 ms

epla.aha.io screenshot

About Website

Visit epla.aha.io now to see the best up-to-date Epla Aha content for India and also check out these interesting facts you probably never knew about epla.aha.io

Visit epla.aha.io

Key Findings

We analyzed Epla.aha.io page load time and found that the first response time was 17 ms and then it took 655 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 10% of websites can load faster.

Performance Metrics

epla.aha.io performance score

31

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value14.4 s

0/100

10%

LCP (Largest Contentful Paint)

Value14.4 s

0/100

25%

SI (Speed Index)

Value14.4 s

1/100

10%

TBT (Total Blocking Time)

Value590 ms

50/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value15.0 s

7/100

10%

Network Requests Diagram

epla.aha.io

17 ms

epla.aha.io

36 ms

new

36 ms

application-1327509a8d46a38fafa24831ee257f92.css

49 ms

application-ca4de3db1b7dc3a62ffa0355c6a7abc2.js

113 ms

Our browser made a total of 11 requests to load all elements on the main page. We found that 55% of them (6 requests) were addressed to the original Epla.aha.io, 18% (2 requests) were made to Google-analytics.com and 9% (1 request) were made to Js-agent.newrelic.com. The less responsive or slowest element that took the longest time to load (113 ms) belongs to the original domain Epla.aha.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 12.5 kB (25%)

Content Size

49.3 kB

After Optimization

36.8 kB

In fact, the total size of Epla.aha.io main page is 49.3 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. Only 10% of websites need less resources to load. Javascripts take 29.9 kB which makes up the majority of the site volume.

HTML Optimization

-64%

Potential reduce by 12.4 kB

  • Original 19.4 kB
  • After minification 19.1 kB
  • After compression 7.0 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 12.4 kB or 64% of the original size.

JavaScript Optimization

-0%

Potential reduce by 50 B

  • Original 29.9 kB
  • After minification 29.9 kB
  • After compression 29.8 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. This website has mostly compressed JavaScripts.

Requests Breakdown

Number of requests can be reduced by 4 (50%)

Requests Now

8

After Optimization

4

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

Accessibility Review

epla.aha.io accessibility score

95

Accessibility Issues

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

epla.aha.io best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

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

epla.aha.io SEO score

85

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Page is blocked from indexing

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Epla.aha.io can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Epla.aha.io 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 description is not detected on the main page of Epla Aha. 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: