3.6 sec in total
223 ms
3.1 sec
300 ms
Welcome to cof.bg homepage info - get ready to check Cof best content right away, or after learning these important things about cof.bg
Евангелска църква на вяра - Пловдив
Visit cof.bgWe analyzed Cof.bg page load time and found that the first response time was 223 ms 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.
cof.bg performance score
name
value
score
weighting
Value3.2 s
44/100
10%
Value9.7 s
0/100
25%
Value6.0 s
47/100
10%
Value0 ms
100/100
30%
Value0.08
94/100
15%
Value3.2 s
94/100
10%
223 ms
167 ms
466 ms
310 ms
319 ms
Our browser made a total of 32 requests to load all elements on the main page. We found that 91% of them (29 requests) were addressed to the original Cof.bg, 6% (2 requests) were made to Google-analytics.com and 3% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Cof.bg.
Page size can be reduced by 241.6 kB (6%)
3.8 MB
3.6 MB
In fact, the total size of Cof.bg main page is 3.8 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. 20% of websites need less resources to load. Images take 3.6 MB which makes up the majority of the site volume.
Potential reduce by 9.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. 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 9.5 kB or 70% of the original size.
Potential reduce by 138.5 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. Cof images are well optimized though.
Potential reduce by 72.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 72.6 kB or 59% of the original size.
Potential reduce by 21.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. Cof.bg needs all CSS files to be minified and compressed as it can save up to 21.0 kB or 79% of the original size.
Number of requests can be reduced by 14 (45%)
31
17
The browser has sent 31 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Cof. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
223 ms
mod_briaskISS.css
167 ms
mootools-core.js
466 ms
core.js
310 ms
caption.js
319 ms
mod_briaskISS.js
324 ms
template.css
332 ms
top-menu.css
330 ms
general.css
463 ms
jquery.min.js
6 ms
ga.js
41 ms
bg.jpg
1172 ms
header-logo.png
620 ms
menu-r.gif
163 ms
menu-l.gif
160 ms
blank-lg.gif
153 ms
wrapper-bg.png
166 ms
bannerFrame.png
304 ms
IMG_2132.jpg
1278 ms
IMG_2130.jpg
1309 ms
DSC_2093.jpg
1318 ms
DSC_1406.jpg
1212 ms
DSC_1242.jpg
1232 ms
IMG_2137.jpg
1524 ms
DSC_1285.jpg
1669 ms
IMG_2172.jpg
1699 ms
list.gif
1414 ms
wrapper-bt.png
1459 ms
footer-top.png
1462 ms
footer-bg.png
1576 ms
footer-bottom.png
1621 ms
__utm.gif
12 ms
cof.bg 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
<frame> or <iframe> elements do not have a title
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.
cof.bg 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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
cof.bg 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 doesn't use legible font sizes
BG
BG
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Cof.bg can be misinterpreted by Google and other search engines. Our service has detected that Bulgarian is used on the page, and it matches the claimed language. Our system also found out that Cof.bg 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.
cof.bg
Open Graph description is not detected on the main page of Cof. 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: