2.9 sec in total
564 ms
2.1 sec
257 ms
Click here to check amazing Funkcje content for Poland. Otherwise, check out these important facts you probably never knew about funkcje.net
Zbiór ponad 4700 Funkcji, Skryptów, Kursów oraz Artykułów dotyczących projektowania stron WWW dla początkujących i zaawansowanych.
Visit funkcje.netWe analyzed Funkcje.net page load time and found that the first response time was 564 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
funkcje.net performance score
name
value
score
weighting
Value4.1 s
22/100
10%
Value8.5 s
1/100
25%
Value5.3 s
58/100
10%
Value10 ms
100/100
30%
Value0.217
57/100
15%
Value4.3 s
85/100
10%
564 ms
225 ms
228 ms
229 ms
229 ms
Our browser made a total of 77 requests to load all elements on the main page. We found that 87% of them (67 requests) were addressed to the original Funkcje.net, 6% (5 requests) were made to Static01.helion.com.pl and 3% (2 requests) were made to Androidpolska.pl. The less responsive or slowest element that took the longest time to load (1 sec) relates to the external source Static01.helion.com.pl.
Page size can be reduced by 131.2 kB (28%)
463.6 kB
332.4 kB
In fact, the total size of Funkcje.net main page is 463.6 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 20% of websites need less resources to load. Images take 243.4 kB which makes up the majority of the site volume.
Potential reduce by 57.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 10.9 kB, which is 16% 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 57.1 kB or 85% of the original size.
Potential reduce by 5.3 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. Funkcje images are well optimized though.
Potential reduce by 68.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 68.2 kB or 46% of the original size.
Potential reduce by 625 B
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. Funkcje.net needs all CSS files to be minified and compressed as it can save up to 625 B or 15% of the original size.
Number of requests can be reduced by 31 (53%)
59
28
The browser has sent 59 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Funkcje. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and as a result speed up the page load time.
funkcje.net
564 ms
tree.js
225 ms
ajaxcore.js
228 ms
ajaxform.js
229 ms
ajaxsuggest.js
229 ms
cache_ajax.js
299 ms
load_form_log.js
300 ms
register.js
228 ms
thx.js
229 ms
okno.js
338 ms
odwiedziy.js
340 ms
ranking.js
341 ms
prototype.js
472 ms
pozycja.js
380 ms
jquery.min.js
495 ms
jquery.cookies.js
451 ms
funkcje_style.css
459 ms
polec_strone.js
493 ms
cache_ajax.js
268 ms
load_form_log.js
276 ms
tlo.jpg
115 ms
Helion_may_the_forth_Rpolony_39b38884a_1180x419.jpg
1025 ms
LOGO_MALE.gif
22 ms
bootgr.jpg
636 ms
scss47.jpg
636 ms
aspnm7.jpg
640 ms
boo4z2.jpg
639 ms
ajax-loader.gif
114 ms
logo.jpg
115 ms
left-search.gif
306 ms
middle-search.gif
322 ms
szukaj-search.jpg
306 ms
php5-power-micro.png
358 ms
mysql_icon.png
346 ms
norton_safe_icon.gif
344 ms
pagerank5.png
419 ms
kreska.jpg
548 ms
no-icon.png
436 ms
git-icon.png
463 ms
php-icon.png
461 ms
sql-icon.png
472 ms
as-icon.png
532 ms
css.gif
346 ms
xhtml.gif
345 ms
pajacyk.gif
333 ms
projekt2_30.gif
333 ms
right-search.jpg
556 ms
fill-menu.gif
570 ms
przycisk1.gif
330 ms
przycisk2.gif
328 ms
przycisk3.gif
442 ms
przycisk4.gif
442 ms
przycisk5.gif
444 ms
belka.png
454 ms
projekt2_20.jpg
455 ms
projekt2_24.png
457 ms
load_form_log.php
679 ms
wycena.jpg
320 ms
projekt2_29.gif
512 ms
ga.js
8 ms
__utm.gif
11 ms
androidpolska.pl
13 ms
tlo.jpg
635 ms
przycisk2.gif
328 ms
projekt2_30.gif
335 ms
przycisk1.gif
342 ms
pajacyk.gif
582 ms
xhtml.gif
443 ms
css.gif
443 ms
przycisk3.gif
352 ms
przycisk4.gif
357 ms
przycisk5.gif
407 ms
belka.png
453 ms
projekt2_20.jpg
451 ms
projekt2_24.png
450 ms
projekt2_29.gif
357 ms
log.gif
286 ms
funkcje.net accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Image elements do not have [alt] attributes
<input type="image"> elements do not have [alt] text
Form elements do not have associated labels
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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Some elements have a [tabindex] value greater than 0
funkcje.net 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
funkcje.net 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
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Funkcje.net 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 Funkcje.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.
funkcje.net
Open Graph description is not detected on the main page of Funkcje. 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: