3.4 sec in total
892 ms
2.3 sec
166 ms
Welcome to corpus.bg homepage info - get ready to check Corpus best content right away, or after learning these important things about corpus.bg
Дизайн и реклама. Корпус ООД е компания предлагаща рекламно обслужване - печатна реклама, интернет реклама, графичен дизайн, Уеб дизайн.
Visit corpus.bgWe analyzed Corpus.bg page load time and found that the first response time was 892 ms and then it took 2.5 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.
corpus.bg performance score
name
value
score
weighting
Value2.5 s
68/100
10%
Value5.3 s
22/100
25%
Value3.9 s
83/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value2.6 s
98/100
10%
892 ms
493 ms
249 ms
247 ms
249 ms
Our browser made a total of 26 requests to load all elements on the main page. We found that 92% of them (24 requests) were addressed to the original Corpus.bg, 8% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Corpus.bg.
Page size can be reduced by 152.6 kB (21%)
734.3 kB
581.6 kB
In fact, the total size of Corpus.bg main page is 734.3 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. 15% of websites need less resources to load. Images take 576.8 kB which makes up the majority of the site volume.
Potential reduce by 33.7 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 33.7 kB or 82% of the original size.
Potential reduce by 47.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. Corpus images are well optimized though.
Potential reduce by 55.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 55.6 kB or 58% of the original size.
Potential reduce by 15.9 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. Corpus.bg needs all CSS files to be minified and compressed as it can save up to 15.9 kB or 82% of the original size.
Number of requests can be reduced by 11 (44%)
25
14
The browser has sent 25 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Corpus. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 5 to 1 for JavaScripts and as a result speed up the page load time.
corpus.bg
892 ms
jquery-1.3.2.min.js
493 ms
jquery.scrollable-1.0.5.js
249 ms
jquery.timers.js
247 ms
main.js
249 ms
main.css
368 ms
scrollable-minimal.css
484 ms
scrollable-navig.css
490 ms
ga.js
5 ms
body_bgr.jpg
124 ms
blocks_bgr.png
245 ms
header_bgr.jpg
252 ms
corpus_logo.jpg
252 ms
535_0_1377258129_tb_Gallery_Trace_big.jpg
658 ms
535_0_1327421651_tmb_website_Ciela_big.jpg
625 ms
535_0_1329810965_Gallery_sportinternational_big.jpg
858 ms
535_0_1332330105_tb_webGallery_Sis_Technology_big.jpg
859 ms
535_0_1300808179_Frontpage_Animex.jpg
991 ms
535_0_1327423508_tb_Great_Wall_web_big.jpg
993 ms
body_line.jpg
870 ms
star.jpg
902 ms
__utm.gif
17 ms
arrow_right.gif
1061 ms
right_light_arrow.gif
1061 ms
arrow_up.gif
1075 ms
arrow_down.gif
1104 ms
corpus.bg 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.
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Definition list items are not wrapped in <dl> elements
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
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
Form elements do not have associated labels
Links do not have a discernible name
corpus.bg SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
BG
BG
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Corpus.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 Corpus.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.
corpus.bg
Open Graph description is not detected on the main page of Corpus. 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: