Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

primo.bg

Уеб достъпът до този сайт е временно ограничен

Page Load Speed

17.3 sec in total

First Response

495 ms

Resources Loaded

13.7 sec

Page Rendered

3 sec

primo.bg screenshot

About Website

Visit primo.bg now to see the best up-to-date Primo content and also check out these interesting facts you probably never knew about primo.bg

Visit primo.bg

Key Findings

We analyzed Primo.bg page load time and found that the first response time was 495 ms and then it took 16.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

primo.bg performance score

0

Network Requests Diagram

primo.bg

495 ms

www.primo.bg

1045 ms

page-defaults-7b5360a.z.css

129 ms

jquery.min.js

173 ms

unbounce.js

120 ms

Our browser made a total of 55 requests to load all elements on the main page. We found that 4% of them (2 requests) were addressed to the original Primo.bg, 38% (21 requests) were made to D9hhrg4mnvzow.cloudfront.net and 18% (10 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (11.7 sec) relates to the external source D9hhrg4mnvzow.cloudfront.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 650.1 kB (5%)

Content Size

12.3 MB

After Optimization

11.6 MB

In fact, the total size of Primo.bg main page is 12.3 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. 45% of websites need less resources to load. Images take 11.7 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 75.3 kB

  • Original 87.5 kB
  • After minification 86.7 kB
  • After compression 12.2 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 75.3 kB or 86% of the original size.

Image Optimization

-2%

Potential reduce by 202.5 kB

  • Original 11.7 MB
  • After minification 11.5 MB

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. Primo images are well optimized though.

JavaScript Optimization

-59%

Potential reduce by 168.7 kB

  • Original 285.3 kB
  • After minification 284.9 kB
  • After compression 116.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 168.7 kB or 59% of the original size.

CSS Optimization

-82%

Potential reduce by 203.5 kB

  • Original 248.0 kB
  • After minification 247.9 kB
  • After compression 44.4 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. Primo.bg needs all CSS files to be minified and compressed as it can save up to 203.5 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 14 (33%)

Requests Now

42

After Optimization

28

The browser has sent 42 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Primo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and as a result speed up the page load time.

SEO Factors

primo.bg SEO score

0

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Primo.bg can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Primo.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.

Social Sharing Optimization

Open Graph description is not detected on the main page of Primo. 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: