3.6 sec in total
706 ms
2.6 sec
236 ms
Click here to check amazing 02 content. Otherwise, check out these important facts you probably never knew about 02.ro
Visit 02.roWe analyzed 02.ro page load time and found that the first response time was 706 ms and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
02.ro performance score
name
value
score
weighting
Value1.6 s
94/100
10%
Value1.6 s
99/100
25%
Value1.6 s
100/100
10%
Value0 ms
100/100
30%
Value0.032
100/100
15%
Value1.6 s
100/100
10%
706 ms
177 ms
290 ms
301 ms
297 ms
Our browser made a total of 42 requests to load all elements on the main page. We found that all of those requests were addressed to 02.ro and no external sources were called. The less responsive or slowest element that took the longest time to load (973 ms) belongs to the original domain 02.ro.
Page size can be reduced by 68.1 kB (45%)
150.4 kB
82.2 kB
In fact, the total size of 02.ro main page is 150.4 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. Only 10% of websites need less resources to load. Javascripts take 64.5 kB which makes up the majority of the site volume.
Potential reduce by 9.4 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 2.8 kB, which is 24% 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 9.4 kB or 80% of the original size.
Potential reduce by 2.9 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. 02 images are well optimized though.
Potential reduce by 41.9 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 41.9 kB or 65% of the original size.
Potential reduce by 14.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. 02.ro needs all CSS files to be minified and compressed as it can save up to 14.0 kB or 76% of the original size.
Number of requests can be reduced by 8 (25%)
32
24
The browser has sent 32 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 02. 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 from 5 to 1 for CSS and as a result speed up the page load time.
02.ro
706 ms
template_css.css
177 ms
s-blue.css
290 ms
p-blue.css
301 ms
body-beige.css
297 ms
jquery.tabs.css
332 ms
jquery-1.3.2.min.js
973 ms
jquery-easing.1.2.pack.js
323 ms
jquery-easing-compatibility.1.2.pack.js
459 ms
coda-slider.1.1.1.pack.js
465 ms
main.js
467 ms
header-bg.png
164 ms
header-logo.png
310 ms
header-shadow-l.png
159 ms
header-shadow-r.png
156 ms
mapped_drive-001.jpg
145 ms
mapped_drive-002.jpg
147 ms
mapped_drive-003.jpg
291 ms
mapped_drive-004.jpg
287 ms
mapped_drive-005.jpg
299 ms
ftp-001.jpg
303 ms
ftp-002.jpg
306 ms
ftp-003.jpg
430 ms
home.gif
403 ms
body2-shadow-l.png
412 ms
body2-shadow-r.png
416 ms
body-shadow-l.png
419 ms
body-shadow-r.png
424 ms
bullet-f.png
543 ms
quote-b-start.png
547 ms
quote-b-end.png
555 ms
bottom-bg.png
559 ms
bottom-shadow-l.png
563 ms
bottom-shadow-r.png
571 ms
bottom-div-l.png
687 ms
bottom-div-r.png
690 ms
footer-bg.png
698 ms
footer-shadow-l.png
703 ms
footer-shadow-r.png
706 ms
ajax-loader.gif
715 ms
arrow-left.gif
148 ms
arrow-right.gif
148 ms
02.ro 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.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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.
02.ro best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
02.ro SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 02.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 02.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.
02.ro
Open Graph description is not detected on the main page of 02. 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: