4.5 sec in total
1.1 sec
2.9 sec
456 ms
Welcome to boromeusz.franciszkanie.pl homepage info - get ready to check Boromeusz Franciszkanie best content for Poland right away, or after learning these important things about boromeusz.franciszkanie.pl
Strona Parafii pw. św. Karola Boromeusza we Wrocławiu i Sanktuarium Matki Bożej Łaskawej Patronki i Opiekunki Małżeństwa i Rodzin
Visit boromeusz.franciszkanie.plWe analyzed Boromeusz.franciszkanie.pl page load time and found that the first response time was 1.1 sec and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
boromeusz.franciszkanie.pl performance score
name
value
score
weighting
Value5.9 s
4/100
10%
Value13.6 s
0/100
25%
Value12.9 s
2/100
10%
Value4,250 ms
1/100
30%
Value0.08
94/100
15%
Value22.6 s
1/100
10%
1139 ms
26 ms
132 ms
170 ms
166 ms
Our browser made a total of 63 requests to load all elements on the main page. We found that 73% of them (46 requests) were addressed to the original Boromeusz.franciszkanie.pl, 10% (6 requests) were made to Fonts.gstatic.com and 5% (3 requests) were made to S.ytimg.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Boromeusz.franciszkanie.pl.
Page size can be reduced by 805.2 kB (9%)
8.6 MB
7.8 MB
In fact, the total size of Boromeusz.franciszkanie.pl main page is 8.6 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. 50% of websites need less resources to load. Images take 7.7 MB which makes up the majority of the site volume.
Potential reduce by 35.5 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 9.8 kB, which is 22% 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 35.5 kB or 80% of the original size.
Potential reduce by 70.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. Boromeusz Franciszkanie images are well optimized though.
Potential reduce by 301.5 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 301.5 kB or 66% of the original size.
Potential reduce by 398.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. Boromeusz.franciszkanie.pl needs all CSS files to be minified and compressed as it can save up to 398.3 kB or 83% of the original size.
Number of requests can be reduced by 26 (46%)
56
30
The browser has sent 56 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Boromeusz Franciszkanie. 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 from 11 to 1 for CSS and as a result speed up the page load time.
boromeusz.franciszkanie.pl
1139 ms
css
26 ms
bootstrap.min.css
132 ms
font-awesome.min.css
170 ms
flexslider.css
166 ms
prettyPhoto.css
174 ms
styles-blue.css
177 ms
search_form.css
182 ms
style.css
223 ms
style.css
249 ms
search_form.css
246 ms
jquery-1.10.2.min.js
418 ms
jquery.cookie.js
255 ms
socialite.min.js
272 ms
jquery-migrate-1.2.1.min.js
290 ms
bootstrap.min.js
309 ms
bootstrap-hover-dropdown.min.js
309 ms
back-to-top.js
317 ms
jquery.placeholder.js
341 ms
jquery.prettyPhoto.js
380 ms
jquery.flexslider-min.js
389 ms
jflickrfeed.min.js
389 ms
main.js
491 ms
analytics.js
85 ms
Qp49px52ayc
140 ms
hqdefault.jpg
170 ms
hqdefault.jpg
258 ms
logo_small3.png
601 ms
703fbf4d6342e7a427ddc6c87fcedbd7.jpg
280 ms
6891113984c451b88257465b46fabdf8.jpg
129 ms
841e558023222732d1711841f99e93e3.jpg
393 ms
4b2820f0c4fe29e2d289589b90e47f4c.png
708 ms
5bd9cffb18e3e7ce61680aa1b1ee9cb8.jpg
392 ms
16b7e70d7717cfdb30fce0b74d7ab193.jpg
1286 ms
37c314c5d6f1bb18e3efbfcf808e99eb.JPG
808 ms
b6e6e28c734a2a405a16d3f417bbb2ed.jpg
419 ms
bg_direction_nav.png
441 ms
029b655aecb894af051994aace0fd1fe.jpg
502 ms
2972c06798b5e5c343ce74212ffed5ef.jpg
526 ms
8982084877bf97676a2205e82c5d01d6.jpg
974 ms
a0a48bd293105e8528f802bba56cd06a.jpg
1337 ms
59cb831df7600ef31cc9366068830676.jpg
900 ms
348b86563ea2f0c04d28617b1ff1b6ab.jpg
988 ms
c5a014051bd74cca88c48565171e71fe.png
992 ms
8f7be2f49d2b3fdfd42b9641d7e6c2ea.jpg
1006 ms
1cb9028c3baae70e48a57967cb160f17.jpg
1165 ms
7aeffa02923145ce2e512c2edb7d7071.jpg
1161 ms
ae1e8f283c3304ab8ed10d9b1f6071ca.png
1305 ms
8095f89642e45efff37683d29c7f9351.jpg
1141 ms
ffcf402ceabc5db2285e4715763e7dbd.jpg
1284 ms
u-WUoqrET9fUeobQW7jkRT8E0i7KZn-EPnyo3HZu7kw.woff
61 ms
DXI1ORHCpsQm3Vp6mXoaTRa1RVmPjeKy21_GQJaLlJI.woff
62 ms
MTP_ySUJH_bn48VBG8sNSha1RVmPjeKy21_GQJaLlJI.woff
65 ms
k3k702ZOKiLJc3WVjuplzBa1RVmPjeKy21_GQJaLlJI.woff
64 ms
fontawesome-webfont.woff
1204 ms
collect
47 ms
www-embed-player-vfl8xM8me.css
66 ms
www-embed-player.js
90 ms
base.js
159 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
46 ms
ad_status.js
55 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
80 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
79 ms
boromeusz.franciszkanie.pl 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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
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.
boromeusz.franciszkanie.pl 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
boromeusz.franciszkanie.pl SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Boromeusz.franciszkanie.pl can be misinterpreted by Google and other search engines. Our service has detected that Polish is used on the page, and it does not match the claimed English language. Our system also found out that Boromeusz.franciszkanie.pl 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.
boromeusz.franciszkanie.pl
Open Graph description is not detected on the main page of Boromeusz Franciszkanie. 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: