3.2 sec in total
504 ms
2.1 sec
614 ms
Welcome to gexe.pl homepage info - get ready to check G Exe best content for Poland right away, or after learning these important things about gexe.pl
Wszystko o grach cRPG, RPG i fantastyce. Najświeższe informacje, recenzje gier i książek, poradniki, konkursy i bogate forum dyskusyjne
Visit gexe.plWe analyzed Gexe.pl page load time and found that the first response time was 504 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
gexe.pl performance score
name
value
score
weighting
Value3.7 s
29/100
10%
Value12.1 s
0/100
25%
Value5.8 s
49/100
10%
Value1,800 ms
10/100
30%
Value0.009
100/100
15%
Value10.8 s
22/100
10%
504 ms
281 ms
190 ms
472 ms
195 ms
Our browser made a total of 116 requests to load all elements on the main page. We found that 19% of them (22 requests) were addressed to the original Gexe.pl, 34% (39 requests) were made to Gfx.gexe.pl and 9% (10 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (943 ms) relates to the external source Gfx.gexe.pl.
Page size can be reduced by 126.3 kB (10%)
1.2 MB
1.1 MB
In fact, the total size of Gexe.pl main page is 1.2 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. 55% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 32.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. 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 32.1 kB or 70% of the original size.
Potential reduce by 61.4 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. G Exe images are well optimized though.
Potential reduce by 9.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 9.8 kB or 21% of the original size.
Potential reduce by 23.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. Gexe.pl needs all CSS files to be minified and compressed as it can save up to 23.0 kB or 79% of the original size.
Number of requests can be reduced by 43 (38%)
114
71
The browser has sent 114 CSS, Javascripts, AJAX and image requests in order to completely render the main page of G Exe. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
gexe.pl
504 ms
style.css
281 ms
fancybox.css
190 ms
jquery-1.4.2.js
472 ms
main-pack.js
195 ms
show_ads.js
6 ms
newestVideos.js
131 ms
blank.gif
300 ms
vampirebloodlines.png
387 ms
blackcrusade120x50.jpg
297 ms
bgloop.jpg
165 ms
background2.jpg
715 ms
sprite.png
577 ms
borderRight.png
165 ms
borderLeft.png
166 ms
back1.png
167 ms
wowcenter120x50.jpg
293 ms
fantastyka120x50.jpg
293 ms
trzynastyschron120x50.jpg
294 ms
yggdrasil-button.png
293 ms
bmfw120x50.jpg
293 ms
tawerna120x50.png
390 ms
blank.gif
291 ms
rssSmall.png
292 ms
swiatyniapierwotnegozlaporadniki.png
390 ms
statklupy.png
390 ms
deadpool.png
289 ms
facebook_ge.png
289 ms
1.png
291 ms
193149.1456770709m.jpg
387 ms
42.png
388 ms
181035.1456765835m.jpeg
485 ms
592.png
461 ms
123627.1456745787.jpg
486 ms
121.png
484 ms
151131.1456668691m.jpg
574 ms
1275.png
484 ms
143320.1456666400m.jpg
641 ms
63.png
578 ms
143244.1456666364m.jpg
580 ms
1397.png
575 ms
190735.1456596455m.jpg
672 ms
184303.1456249383m.jpg
674 ms
34.png
674 ms
103705.1455356225.jpg
675 ms
215423.1456520063m.jpg
773 ms
174642.1456246002.jpg
731 ms
174445.1456245885.jpg
760 ms
174348.1456245828.jpg
763 ms
171557.1456244157.jpg
760 ms
170919.1456243759.jpg
766 ms
105941.1454579981.jpg
828 ms
110113.1454580073.jpg
898 ms
173825.1430840305.jpg
899 ms
taern.jpg
899 ms
facebook.png
899 ms
nk.png
899 ms
youtube.png
910 ms
lastfm.gif
943 ms
zrt_lookup.html
30 ms
show_ads_impl.js
47 ms
ads
256 ms
sprite2.png
103 ms
backContent.png
102 ms
kostka.gif
102 ms
osd.js
68 ms
ads
242 ms
external_link.gif
125 ms
leftMenu.png
173 ms
menuHead.png
173 ms
unMenuHeader.png
173 ms
menuItem.gif
200 ms
centerMenu.png
295 ms
menuAdLeft.png
271 ms
ads
176 ms
ga.js
53 ms
plusone.js
128 ms
playlistItems
896 ms
__utm.gif
27 ms
twitter.jpg
665 ms
26135116.gif
673 ms
vampirebloodlines.jpg
865 ms
collect
72 ms
cb=gapi.loaded_0
13 ms
163035407530238160
43 ms
abg.js
41 ms
m_js_controller.js
40 ms
googlelogo_color_112x36dp.png
94 ms
1215506591548907880
66 ms
likebox.php
301 ms
s
33 ms
redir.html
91 ms
x_button_blue2.png
10 ms
E4WYPs_lNJIuXrWpTsOcc3FIG36RfI0ERc0srw5QW9Y.js
11 ms
iframe.html
34 ms
xYm_UD1pmAz.css
88 ms
TGpOWuX6Pv8.css
106 ms
_rx8naC75Dy.js
145 ms
x5F9OMjKyLw.js
173 ms
ICDbTSzjQEg.js
144 ms
TTCre3391I0.js
142 ms
12042743_10153343499883323_6777791588703239368_n.jpg
87 ms
417046_10150565858978323_883485215_n.jpg
76 ms
10983152_570751286393351_8829510945189496126_n.jpg
88 ms
301987_101882923258472_1154970617_n.jpg
114 ms
11350757_502852189883891_4829143313056056764_n.jpg
93 ms
12241448_628629163907012_4266144061260248362_n.jpg
94 ms
943907_219566951721616_7990805182780586118_n.jpg
114 ms
12729119_1560626240918396_8224606824820966680_n.jpg
96 ms
wL6VQj7Ab77.png
20 ms
s7jcwEQH7Sx.png
19 ms
I6-MnjEovm5.js
20 ms
vlXaquuXMrr.js
36 ms
default.jpg
24 ms
default.jpg
31 ms
default.jpg
40 ms
gexe.pl 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-*] attributes do not match their roles
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
gexe.pl best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
gexe.pl SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 uses legible font sizes
Tap targets are not sized appropriately
PL
PL
ISO-8859-2
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Gexe.pl can be misinterpreted by Google and other search engines. Our service has detected that Polish is used on the page, and it matches the claimed language. Our system also found out that Gexe.pl main page’s claimed encoding is iso-8859-2. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
gexe.pl
Open Graph description is not detected on the main page of G Exe. 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: