Tools & Wizards About Us
ollin.ro screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

ollin.ro

My Blog – My WordPress Blog

Page Load Speed

4 sec in total

First Response

839 ms

Resources Loaded

3 sec

Page Rendered

199 ms

ollin.ro screenshot

About Website

Welcome to ollin.ro homepage info - get ready to check Ollin best content right away, or after learning these important things about ollin.ro

descriere

Visit ollin.ro

Key Findings

We analyzed Ollin.ro page load time and found that the first response time was 839 ms and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

ollin.ro performance score

0

Network Requests Diagram

ollin.ro

839 ms

www.ollin.ro

836 ms

style.css

275 ms

jquery.fancybox-1.2.6.css

315 ms

jquery.jcarousel.css

552 ms

Our browser made a total of 29 requests to load all elements on the main page. We found that 93% of them (27 requests) were addressed to the original Ollin.ro, 7% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (839 ms) belongs to the original domain Ollin.ro.

Page Optimization Overview & Recommendations

Page size can be reduced by 86.5 kB (34%)

Content Size

253.1 kB

After Optimization

166.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ollin.ro main page is 253.1 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 127.4 kB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 5.0 kB

  • Original 7.1 kB
  • After minification 6.2 kB
  • After compression 2.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 949 B, which is 13% 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 5.0 kB or 71% of the original size.

Image Optimization

-6%

Potential reduce by 7.9 kB

  • Original 127.4 kB
  • After minification 119.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. Ollin images are well optimized though.

JavaScript Optimization

-53%

Potential reduce by 45.0 kB

  • Original 84.6 kB
  • After minification 83.5 kB
  • After compression 39.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 45.0 kB or 53% of the original size.

CSS Optimization

-84%

Potential reduce by 28.6 kB

  • Original 34.0 kB
  • After minification 27.9 kB
  • After compression 5.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. Ollin.ro needs all CSS files to be minified and compressed as it can save up to 28.6 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 4 (15%)

Requests Now

27

After Optimization

23

  • Images
  • JavaScript
  • CSS

The browser has sent 27 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ollin. 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.

Network Requests Diagram

ollin.ro

ollin.ro

839 ms

www.ollin.ro

www.ollin.ro

836 ms

style.css

style.css

275 ms

jquery.fancybox-1.2.6.css

jquery.fancybox-1.2.6.css

315 ms

jquery.jcarousel.css

jquery.jcarousel.css

552 ms

jquery.min.js

jquery.min.js

636 ms

jquery.dropdownPlain.js

jquery.dropdownPlain.js

578 ms

hover.js

hover.js

532 ms

swfobject.js

swfobject.js

594 ms

bg.jpg

bg.jpg

602 ms

header.jpg

header.jpg

272 ms

home_btn.jpg

home_btn.jpg

256 ms

emailboxnews.jpg

emailboxnews.jpg

245 ms

btn_abonez.jpg

btn_abonez.jpg

255 ms

consultanta_top.jpg

consultanta_top.jpg

259 ms

bulet_h.jpg

bulet_h.jpg

379 ms

consultanta_btm.jpg

consultanta_btm.jpg

385 ms

footer.jpg

footer.jpg

497 ms

bg_cauta.jpg

bg_cauta.jpg

380 ms

ch_buton.jpg

ch_buton.jpg

382 ms

footer_ph.jpg

footer_ph.jpg

491 ms

footer_mail.jpg

footer_mail.jpg

498 ms

footer_rss.jpg

footer_rss.jpg

503 ms

footer_tw.jpg

footer_tw.jpg

505 ms

footer_in.jpg

footer_in.jpg

615 ms

footer_fb.jpg

footer_fb.jpg

620 ms

nicety.jpg

nicety.jpg

622 ms

ga.js

ga.js

52 ms

__utm.gif

__utm.gif

27 ms

SEO Factors

ollin.ro SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ollin.ro can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Ollin.ro 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

ollin.ro

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