Report Summary

  • 36

    Performance

    Renders faster than
    56% of other websites

  • 69

    Accessibility

    Visual factors better than
    that of 35% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 93

    SEO

    Google-friendlier than
    84% of websites

epis.bg

Epis - информацията, която търсите

Page Load Speed

3.6 sec in total

First Response

571 ms

Resources Loaded

2.6 sec

Page Rendered

409 ms

epis.bg screenshot

About Website

Welcome to epis.bg homepage info - get ready to check Epis best content for Bulgaria right away, or after learning these important things about epis.bg

Полезна информация от всички сфери. Обяснение на нещата, които търсите. Вземете правилните и печеливши решения с Epis.

Visit epis.bg

Key Findings

We analyzed Epis.bg page load time and found that the first response time was 571 ms and then it took 3 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

epis.bg performance score

36

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

69/100

10%

LCP (Largest Contentful Paint)

Value3.8 s

55/100

25%

SI (Speed Index)

Value12.9 s

2/100

10%

TBT (Total Blocking Time)

Value17,460 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value25.5 s

0/100

10%

Network Requests Diagram

epis.bg

571 ms

471 ms

818 ms

cyr.js

160 ms

platform.js

70 ms

Our browser made a total of 63 requests to load all elements on the main page. We found that 32% of them (20 requests) were addressed to the original Epis.bg, 17% (11 requests) were made to Apis.google.com and 10% (6 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Epis.bg.

Page Optimization Overview & Recommendations

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

Content Size

999.3 kB

After Optimization

846.9 kB

In fact, the total size of Epis.bg main page is 999.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. 70% of websites need less resources to load. Images take 787.4 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 62.4 kB

  • Original 75.8 kB
  • After minification 70.2 kB
  • After compression 13.3 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 62.4 kB or 82% of the original size.

Image Optimization

-6%

Potential reduce by 45.4 kB

  • Original 787.4 kB
  • After minification 742.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. Epis images are well optimized though.

JavaScript Optimization

-33%

Potential reduce by 44.6 kB

  • Original 136.2 kB
  • After minification 136.0 kB
  • After compression 91.6 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 44.6 kB or 33% of the original size.

Requests Breakdown

Number of requests can be reduced by 27 (49%)

Requests Now

55

After Optimization

28

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

Accessibility Review

epis.bg accessibility score

69

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

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

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

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

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

epis.bg best practices score

58

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

epis.bg SEO score

93

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

    BG

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Epis.bg can be misinterpreted by Google and other search engines. Our service has detected that Bulgarian 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 Epis.bg 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 Epis. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: