Access e-frag.net. Loading...

Report Summary

About Website

Visit e-frag.net now to see the best up-to-date E Frag content for Russia and also check out these interesting facts you probably never knew about e-frag.net

E-Frag - formed in 2011, aims to become leading gaming portal focused on counter-strike: global offensive

Visit e-frag.net

name

value

score

weighting

FCP (First Contentful Paint)

Value5.0 s

9/100

10%

LCP (Largest Contentful Paint)

Value5.3 s

21/100

25%

SI (Speed Index)

Value5.6 s

53/100

10%

TBT (Total Blocking Time)

Value200 ms

90/100

30%

CLS (Cumulative Layout Shift)

Value0.105

88/100

15%

TTI (Time to Interactive)

Value5.7 s

68/100

10%

www.e-frag.net

659 ms

sweetalert.css

28 ms

g@pefv1.css

6 ms

jquery.min.js

26 ms

jquery.lavalamp.min.js

30 ms

Our browser made a total of 123 requests to load all elements on the main page. We found that 92% of them (113 requests) were addressed to the original E-frag.net, 3% (4 requests) were made to Pagead2.googlesyndication.com and 2% (3 requests) were made to Googleads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (659 ms) belongs to the original domain E-frag.net.

Content Size

8.8 MB

After Optimization

7.1 MB

In fact, the total size of E-frag.net main page is 8.8 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. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 7.5 MB which makes up the majority of the site volume.

HTML Optimization

-91%

Potential reduce by 158.4 kB

Original 174.5 kB
After minification 109.9 kB
After compression 16.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 64.6 kB, which is 37% 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 158.4 kB or 91% of the original size.

Image Optimization

-9%

Potential reduce by 668.2 kB

Original 7.5 MB
After minification 6.8 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. E Frag images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 501.1 kB

Original 750.4 kB
After minification 685.0 kB
After compression 249.3 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 501.1 kB or 67% of the original size.

CSS Optimization

-84%

Potential reduce by 349.5 kB

Original 414.5 kB
After minification 380.7 kB
After compression 65.0 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. E-frag.net needs all CSS files to be minified and compressed as it can save up to 349.5 kB or 84% of the original size.

Requests Now

115

After Optimization

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

Accessibility Issues

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

Document doesn't have a <title> element

High

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

Areas of Improvement

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

Low

Detected JavaScript libraries

High

Page has valid source maps

Search Engine Optimization Advices

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

High

Document doesn't have a <title> element

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

High

Page is blocked from indexing

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 doesn't use legible font sizes

Language and Encoding

Language Detected

N/A
Language Claimed

N/A
Encoding

UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise E-frag.net can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that E-frag.net 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

e-frag.net

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

Report Summary

Performance

Accessibility

Best Practices

SEO

Loading...

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)