3.6 sec in total
451 ms
2.8 sec
383 ms
Visit egb.com now to see the best up-to-date EGB content for United Kingdom and also check out these interesting facts you probably never knew about egb.com
EGB is one of the best esports betting websites. Bets on CS GO, Dota 2, League of Legends, Overwatch and other popular titles are waiting for you!
Visit egb.comWe analyzed Egb.com page load time and found that the first response time was 451 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
egb.com performance score
name
value
score
weighting
Value4.3 s
18/100
10%
Value33.8 s
0/100
25%
Value19.2 s
0/100
10%
Value35,290 ms
0/100
30%
Value0.056
98/100
15%
Value51.4 s
0/100
10%
451 ms
36 ms
35 ms
205 ms
203 ms
Our browser made a total of 115 requests to load all elements on the main page. We found that 49% of them (56 requests) were addressed to the original Egb.com, 14% (16 requests) were made to Images.egamingbets.com and 10% (11 requests) were made to Vk.com. The less responsive or slowest element that took the longest time to load (752 ms) relates to the external source Images.egamingbets.com.
Page size can be reduced by 531.3 kB (42%)
1.3 MB
727.2 kB
In fact, the total size of Egb.com main page is 1.3 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. 70% of websites need less resources to load. Images take 611.6 kB which makes up the majority of the site volume.
Potential reduce by 101.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 22.7 kB, which is 18% 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 101.1 kB or 82% of the original size.
Potential reduce by 90.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. Obviously, EGB needs image optimization as it can save up to 90.0 kB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 302.4 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 302.4 kB or 64% of the original size.
Potential reduce by 37.7 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. Egb.com needs all CSS files to be minified and compressed as it can save up to 37.7 kB or 79% of the original size.
Number of requests can be reduced by 55 (50%)
111
56
The browser has sent 111 CSS, Javascripts, AJAX and image requests in order to completely render the main page of EGB. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and as a result speed up the page load time.
egb.com
451 ms
home-377e543b6c11e892b77c73b88677a52d5241e61731d1705eec6b183271da4b8d.css
36 ms
home-7dd35295fb6cbdd8b8c2e6d20a7428b7848c58ca9cb4b2312b248522a1fc2d05.js
35 ms
api.js
205 ms
ajax.php
203 ms
en.png
457 ms
cn.png
680 ms
cz.png
255 ms
de.png
256 ms
es.png
251 ms
fr.png
752 ms
it.png
259 ms
kr.png
257 ms
ru.png
260 ms
se.png
261 ms
pl.png
291 ms
1337082687_complete1.png
263 ms
1337083100_complete2.png
291 ms
1337085195_complete3.png
292 ms
1337085605_complete5.png
294 ms
1337085527_complete4-3-years.png
295 ms
egb-logo-f441fb3f0802ecdc3f27e074ac614e1cb56e4b611a791c46f3dd83c2efa95a64.png
32 ms
key-e8642d88e781d5277abe473d7f3e1662f33ac828fc44746302bec869b0c0239e.png
35 ms
chat_popup.js
74 ms
openapi.js
744 ms
openstrim-f1ca51953976ef1bc919de1aea2a0e54dfdb25c293a76d222157745ba2d152ee.png
28 ms
actions-arrow-805be76231af93d0f49a309c5bc34e054229d67fcfe2e98b78bdfe86e2ef29e7.png
41 ms
online-support-7b1bb8c74f1a5846143893c3993ca4d2c4277d8544015fe7e3d64f21ad4e041d.png
29 ms
pl.gif
42 ms
logo-small-5ed12f93d9c4682e3d91ff2707291b89667172c48ca4107ec8620da62ec4b412.png
40 ms
visa-a5546f4f41a6906b2e9576ea5183d222ce40138a6d24eb03dde26c10a40dc6d9.png
42 ms
mastercard-ef18102023e15d202c0446bc8d02f84d941855b2f2962119235018eba0eb2e7b.png
53 ms
neteller-1c8b721f21805209c8fa744f0531f9fbe44c3dadba687d285be895ab59a51830.png
48 ms
paysafecard-2802665d8a186e5162e11b71713fe0e5d902b6d88ef489b186e940b2d1dd9d45.png
49 ms
skrill-bd613f906889429a51c886d75a78f77aaad36c8bc7edbc4fc5891ee97c629cd7.png
53 ms
alipay.png
50 ms
webmoney-2c23c301944c1e77ce8d834b508816f38a82a316ca24d5a2bcf5ff3a11017df6.png
50 ms
qiwi-882be51333f451de5a29c6d70be72c43c52a80aca4df212dbbae35e5a7f92845.png
36 ms
yandexmoney-7b06884506b0f4d566e83adcae484919c92952b086abf09a2fb760921b8ec5e0.png
38 ms
sms-5b7f0098dd7e31eba0e2f73391150d1d561ec07c01403648f096a81cb8bd585b.png
37 ms
18plusicon-9adf99e209cbf976027ed3e4cda3a507c74684d525936264cd154d4f2c12c168.png
35 ms
recaptcha__en.js
73 ms
sdk.js
320 ms
widgets.js
114 ms
platform.js
166 ms
ga.js
18 ms
watch.js
190 ms
__utm.gif
71 ms
cb=gapi.loaded_0
23 ms
cb=gapi.loaded_1
54 ms
fastbutton
89 ms
watch.js
752 ms
postmessageRelay
103 ms
cb=gapi.loaded_0
24 ms
cb=gapi.loaded_1
18 ms
api.js
32 ms
core:rpc:shindig.random:shindig.sha1.js
114 ms
2536007149-postmessagerelay.js
80 ms
173 ms
xd_arbiter.php
241 ms
xd_arbiter.php
588 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
50 ms
stream
235 ms
chat
340 ms
ajax.php
200 ms
info
200 ms
count_open_matches
601 ms
button.831500944bc3eb7ea5276ccdc3f71d2e.js
210 ms
header-bg-fea8ffa1670013ebec44d6a28dd23cb0815bf96257f72622cc24e1c1f891a19f.png
36 ms
v-line-913384566ff870c183c03d9d618940a07117a5192f2d89553aef1efc0315fc1a.png
36 ms
login-field-bg-0a322197b5d7cd790f3fb5e321874a693ec981d7f564c1518859922462877d74.png
37 ms
downarrow-4e59f0995e00de70d4857513fd67f488b4d49f9072acbadacc9718afc0f8fc3a.gif
37 ms
content-bg-23e81002bf3f216b4059428bca9d7c48cce9f8409c6facb9e8ae1238060fceea.png
37 ms
header-bg-c80f94db18bb35461e4ac8d3dcc6a51f319b4be823e2edad05a80bae27428768.gif
78 ms
home-g1-6819b82036e014a1f2df3e88a3a45fc8a9a9f77430d4e416da969de3ae74ac73.jpg
78 ms
home-g2-29ac7d381f8f72ab975de19203afca43b032424cc8aee19f61b7d13d1239f237.jpg
78 ms
home-g3-4e4811474de00c23b75cc9ce6c3a4af1b723dd8fffdb74d8f452e97c52cd3f7f.jpg
95 ms
home-g4-4634750d371b536cbf6f83cfd258d4230171b7d39100a815377eac57ff8e1165.jpg
95 ms
home-actions-fb913d246741fcbc358a515f03b44e623ec6bb717ab0c1c354842cd86fbfc03a.jpg
96 ms
home-news-943c6c93a4be6524a46baf34080400087379d179c884348539eb48eddfa9bd98.jpg
97 ms
action-border-f6a0403dfc47d0fde9022608232139494175c7696359f1cd6c2718be213ce465.png
97 ms
action-button-d8c73b7102b186cd86fa96bee8a8a5a3a668faa2f790b7ccae5e59256cd17c00.png
98 ms
socseti-367455bd8f65a558f5d42f2812431ac1065edeecbc754a44ba3ada8367bbe412.png
99 ms
arrow-left-2a9369ada501eb3ec7020e8e2ad5f60de53abb065c95ba769921044187c136a8.png
99 ms
arrow-right-eac73c7bb2007c4009fd1810d67ab65aed63c20ef98173f2a5e9d67c896ffb46.png
97 ms
slider-arrow-55e09725c5d7ca0d31c3a77682c00a1413af84ebe2723d4fc84244f021e118a0.png
90 ms
upload.gif
567 ms
glyphicons-halflings-regular-a26394f7ede100ca118eff2eda08596275a9839b959c226e15439557a5a80742.woff
568 ms
widget_like.php
574 ms
advert.gif
469 ms
ajax.php
495 ms
like.php
467 ms
facepalm.png
65 ms
people5.png
67 ms
me_gusta.png
65 ms
please.png
69 ms
face1.png
185 ms
lol.png
67 ms
character4.png
195 ms
people.png
66 ms
m262.png
191 ms
rU2ubZ6l1Q5.js
492 ms
LVx-xkvaJ0b.png
550 ms
1
124 ms
loader_nav19130_3.js
139 ms
lite.css
255 ms
lite.js
510 ms
lang3_0.js
259 ms
widgets.css
263 ms
xdm.js
268 ms
al_like.js
269 ms
tweet_button.6a78875565a912489e9aef879c881358.en.html
68 ms
jot
97 ms
like_widget.png
130 ms
nr-885.min.js
24 ms
egb.com accessibility score
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
[aria-hidden="true"] elements contain focusable descendents
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
egb.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
egb.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
Document doesn't use legible font sizes
Tap targets are not sized appropriately
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Egb.com 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 Egb.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.
egb.com
Open Graph description is not detected on the main page of EGB. 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: