Access entry.bg. Entry - N3 - Цифрова телевизия и Интернет

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

45/100

10%

LCP (Largest Contentful Paint)

Value7.0 s

6/100

25%

SI (Speed Index)

Value9.9 s

10/100

10%

TBT (Total Blocking Time)

Value520 ms

56/100

30%

CLS (Cumulative Layout Shift)

Value0.053

98/100

15%

TTI (Time to Interactive)

Value21.3 s

1/100

10%

entry.bg

911 ms

jquery.min.js

479 ms

gallery-float-fix.js

241 ms

jquery.fancybox.css

258 ms

jquery.fancybox.js

548 ms

Our browser made a total of 98 requests to load all elements on the main page. We found that 39% of them (38 requests) were addressed to the original Entry.bg, 39% (38 requests) were made to Maps.googleapis.com and 7% (7 requests) were made to Maps.gstatic.com. The less responsive or slowest element that took the longest time to load (2.8 sec) relates to the external source Maps.googleapis.com.

Content Size

3.6 MB

After Optimization

2.7 MB

In fact, the total size of Entry.bg main page is 3.6 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. 60% of websites need less resources to load. Images take 2.4 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 20.0 kB

Original 25.6 kB
After minification 21.3 kB
After compression 5.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. This page needs HTML code to be minified as it can gain 4.3 kB, which is 17% 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 20.0 kB or 78% of the original size.

Image Optimization

-4%

Potential reduce by 90.9 kB

Original 2.4 MB
After minification 2.3 MB

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. Entry images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 782.7 kB

Original 1.1 MB
After minification 1.1 MB
After compression 351.2 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 782.7 kB or 69% of the original size.

CSS Optimization

-85%

Potential reduce by 34.2 kB

Original 40.3 kB
After minification 29.7 kB
After compression 6.1 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. Entry.bg needs all CSS files to be minified and compressed as it can save up to 34.2 kB or 85% of the original size.

Requests Now

After Optimization

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

Accessibility Issues

These are opportunities to improve the legibility of your content.

High

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

These are opportunities to improve keyboard navigation in your application.

High

Heading elements are not in a sequentially-descending order

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.

High

Image elements do not have [alt] attributes

These items highlight common accessibility best practices.

High

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

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

High

Serves images with low resolution

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

Search Engine Optimization Advices

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

High

Links are not crawlable

Format your HTML in a way that enables crawlers to better understand your app’s content.

High

Image elements do not have [alt] attributes

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/).

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

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 Entry.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 Entry.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

entry.bg

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

Report Summary

Performance

Accessibility

Best Practices

SEO

Entry - N3 - Цифрова телевизия и Интернет

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

entry.bg

jquery.min.js

gallery-float-fix.js

jquery.fancybox.css

jquery.fancybox.js

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

entry.bg

jquery.min.js

gallery-float-fix.js

jquery.fancybox.css

jquery.fancybox.js

jquery.cookie.js

core.css

style.css

jquery-ui.css

jquery.bgiframe-2.1.2.js

jquery-ui.min.js

WebResource.axd

Telerik.Web.UI.WebResource.axd

TweenMax.min.js

header-animation.js

responsive-menu.js

logo.png

channels.png

tv.jpg

internet.jpg

header-n3play.jpg

tv-net.png

packages.jpg

new-users.jpg

registered-users.jpg

cashterminal.jpg

easypay.jpg

imagehandler.jpg

footer-login.png

footer-form.png

footer-contacts.png

tv.jpg

button.png

contact-icon.png

internet.jpg

header-text-n3play.png

packages.jpg

n3-news.jpg

n3-contacts.jpg

ga.js

__utm.gif

collect

mon.js