5.3 sec in total
910 ms
4.2 sec
190 ms
Welcome to gig.eu homepage info - get ready to check GIG best content for Poland right away, or after learning these important things about gig.eu
GIG to nowoczesny instytut badawczy, o uznanej pozycji w świecie, wdrażający innowacyjne wyniki swoich prac oraz wpływający na kształtowanie zrównoważonego rozwoju regionu i kraju.
Visit gig.euWe analyzed Gig.eu page load time and found that the first response time was 910 ms and then it took 4.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
gig.eu performance score
name
value
score
weighting
Value9.1 s
0/100
10%
Value21.6 s
0/100
25%
Value22.0 s
0/100
10%
Value3,060 ms
2/100
30%
Value0.33
34/100
15%
Value27.8 s
0/100
10%
910 ms
228 ms
229 ms
230 ms
237 ms
Our browser made a total of 57 requests to load all elements on the main page. We found that 91% of them (52 requests) were addressed to the original Gig.eu, 4% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to Ssl.gostats.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Gig.eu.
Page size can be reduced by 362.7 kB (34%)
1.1 MB
701.7 kB
In fact, the total size of Gig.eu main page is 1.1 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. 25% of websites need less resources to load. Images take 603.5 kB which makes up the majority of the site volume.
Potential reduce by 29.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 29.1 kB or 77% of the original size.
Potential reduce by 18.7 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. GIG images are well optimized though.
Potential reduce by 199.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 199.6 kB or 70% of the original size.
Potential reduce by 115.3 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. Gig.eu needs all CSS files to be minified and compressed as it can save up to 115.3 kB or 83% of the original size.
Number of requests can be reduced by 44 (80%)
55
11
The browser has sent 55 CSS, Javascripts, AJAX and image requests in order to completely render the main page of GIG. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and from 31 to 1 for CSS and as a result speed up the page load time.
pl
910 ms
system.base.css
228 ms
system.menus.css
229 ms
system.messages.css
230 ms
system.theme.css
237 ms
jquery.ui.core.css
239 ms
jquery.ui.theme.css
492 ms
jquery.ui.button.css
449 ms
jquery.ui.resizable.css
451 ms
jquery.ui.dialog.css
459 ms
simplenews.css
468 ms
date.css
470 ms
datepicker.1.7.css
681 ms
field.css
682 ms
node.css
679 ms
search.css
686 ms
user.css
689 ms
extlink.css
721 ms
views.css
903 ms
ckeditor.css
910 ms
colorbox_style.css
913 ms
ctools.css
909 ms
ldap_servers.admin.css
918 ms
flexslider_img.css
939 ms
flexslider.css
1126 ms
eu_cookie_compliance.css
1129 ms
reset.css
1142 ms
html-elements.css
1144 ms
layout.css
1263 ms
groundwork.css
1270 ms
formalize.css
1349 ms
local.css
1474 ms
js_xAPl0qIk9eowy_iS9tNkCWXLUVoat94SQT48UBCFkyQ.js
1507 ms
js_Ohtm-rFJ0XNT-5s2mWFHGwo0EWpCsHX-v1ItjhVrGoY.js
1528 ms
js_X6l5-8nYNo2R-RyO5ufnRGwEOl_a_B18cFSIGvPiDcY.js
1525 ms
js_rmp2ETX6-7FVTKaAuAOOTjOPHRCAgzumNE2bzJS2JyU.js
1525 ms
counter.js
103 ms
js_xnDYBF_-nZp9HYBX-_kbjU5KLK-hNwyxE63MnBfiO_Y.js
1439 ms
js_eX8Rq9H1rj0NYR1t54LePEdHcHwaTL5Oo-6RRv54r_o.js
1476 ms
ga.js
28 ms
__utm.gif
25 ms
back.jpg
757 ms
white-stripe.jpg
152 ms
top17.jpg
669 ms
intragig.png
232 ms
mail.png
234 ms
login.png
312 ms
lang.png
381 ms
icon-search.png
452 ms
a_20160229.jpg
672 ms
sonda_baner.jpg
647 ms
a_porozumienie_0.jpg
732 ms
smolinski.jpg
686 ms
so5_0.jpg
1090 ms
a_jsm_0.jpg
1001 ms
collect
55 ms
count
129 ms
gig.eu accessibility score
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
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
gig.eu best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
gig.eu 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
PL
PL
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Gig.eu 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 Gig.eu 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.
gig.eu
Open Graph description is not detected on the main page of GIG. 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: