3.2 sec in total
240 ms
2.7 sec
295 ms
Welcome to decodare.info homepage info - get ready to check Decodare best content for Romania right away, or after learning these important things about decodare.info
Decodare telefoane si verificari IMEI. Orange, Vodafone, Samsung, Iphone, Huawei, LG, Alcatel, Blackberry, Nokia, Microsoft | Instructiuni complete | Rapid, sigur, ieftin.
Visit decodare.infoWe analyzed Decodare.info page load time and found that the first response time was 240 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
decodare.info performance score
name
value
score
weighting
Value3.4 s
36/100
10%
Value5.6 s
18/100
25%
Value6.4 s
41/100
10%
Value1,210 ms
20/100
30%
Value0.033
100/100
15%
Value12.0 s
16/100
10%
240 ms
370 ms
143 ms
219 ms
11 ms
Our browser made a total of 93 requests to load all elements on the main page. We found that 20% of them (19 requests) were addressed to the original Decodare.info, 23% (21 requests) were made to Static.xx.fbcdn.net and 10% (9 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Decodare.info.
Page size can be reduced by 409.9 kB (42%)
983.5 kB
573.6 kB
In fact, the total size of Decodare.info main page is 983.5 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. 70% of websites need less resources to load. Javascripts take 532.1 kB which makes up the majority of the site volume.
Potential reduce by 40.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 40.2 kB or 76% of the original size.
Potential reduce by 2.1 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. Decodare images are well optimized though.
Potential reduce by 320.8 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 320.8 kB or 60% of the original size.
Potential reduce by 46.8 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. Decodare.info needs all CSS files to be minified and compressed as it can save up to 46.8 kB or 81% of the original size.
Number of requests can be reduced by 58 (65%)
89
31
The browser has sent 89 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Decodare. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 41 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
decodare.info
240 ms
www.decodare.info
370 ms
style.css
143 ms
jquery-ui-1.10.3.custom.min.css
219 ms
adsbygoogle.js
11 ms
jquery-1.10.2.min.js
333 ms
jquery-ui-1.10.3.custom.min.js
520 ms
scrollTo.js
148 ms
myfunctions.js
148 ms
ga.js
71 ms
sdk.js
279 ms
online
177 ms
cse.js
64 ms
199612.jpg
623 ms
piwik.js
219 ms
decodare-pe-imei-logo3.png
408 ms
plata-cu-paypal.png
88 ms
login_decodare.png
87 ms
ui-bg_flat_55_fbec88_40x100.png
162 ms
ui-icons_2e83ff_256x240.png
160 ms
chat-decodare-pe-imei.png
241 ms
img01.jpg
242 ms
152388.jpg
432 ms
ca-pub-7215876951046007.js
126 ms
zrt_lookup.html
63 ms
show_ads_impl.js
62 ms
cse.js
279 ms
__utm.gif
24 ms
ads
404 ms
osd.js
9 ms
142 ms
xd_arbiter.php
268 ms
xd_arbiter.php
526 ms
jsapi
129 ms
plusone.js
127 ms
skype-uri.js
35 ms
session_active.php
1122 ms
ui-bg_glass_95_fef1ec_1x400.png
84 ms
ui-icons_cd0a0a_256x240.png
84 ms
skype-analytics.js
8 ms
share_button.php
92 ms
default+ro.css
5 ms
default+ro.I.js
20 ms
like.php
128 ms
default.css
16 ms
cb=gapi.loaded_0
54 ms
cb=gapi.loaded_1
101 ms
fastbutton
166 ms
async-ads.js
127 ms
google_custom_search_watermark.gif
80 ms
small-logo.png
103 ms
search_box_icon.png
102 ms
clear.png
104 ms
nav_logo114.png
129 ms
vpc6VNjRPXV.js
571 ms
LVx-xkvaJ0b.png
448 ms
post.php
176 ms
m_js_controller.js
135 ms
abg.js
152 ms
vpc6VNjRPXV.js
618 ms
postmessageRelay
82 ms
cb=gapi.loaded_0
48 ms
cb=gapi.loaded_1
45 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
103 ms
googlelogo_color_112x36dp.png
96 ms
nessie_icon_tiamat_white.png
29 ms
api.js
74 ms
core:rpc:shindig.random:shindig.sha1.js
112 ms
2536007149-postmessagerelay.js
111 ms
jTuqQ-OPDr6.css
306 ms
dbNRhrdsQao.css
310 ms
cMg1NADyTLV.css
374 ms
n370yiaI2G6.css
365 ms
1-xIpmMldel.css
468 ms
bpBnEqBgpVX.css
385 ms
_rx8naC75Dy.js
499 ms
x5F9OMjKyLw.js
572 ms
ICDbTSzjQEg.js
479 ms
b_6HNn_J2BZ.js
482 ms
7cm7D75Y0Sf.js
595 ms
rFmE1g6Dkoz.js
707 ms
336JejShbZp.js
550 ms
njO1TPvGzoR.js
566 ms
TTCre3391I0.js
569 ms
s
12 ms
x_button_blue2.png
21 ms
E4WYPs_lNJIuXrWpTsOcc3FIG36RfI0ERc0srw5QW9Y.js
14 ms
10423264_855559881134050_5628736363732227513_n.jpg
250 ms
23721_488806671142708_1067165460_n.png
291 ms
QDwYpIaRyfG.png
70 ms
I6-MnjEovm5.js
70 ms
vlXaquuXMrr.js
78 ms
activeview
15 ms
decodare.info 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.
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
<frame> or <iframe> elements do not have a title
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
decodare.info 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
Page has valid source maps
decodare.info SEO score
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
Tap targets are not sized appropriately
RO
RO
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Decodare.info can be misinterpreted by Google and other search engines. Our service has detected that Romanian is used on the page, and it matches the claimed language. Our system also found out that Decodare.info 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.
decodare.info
Open Graph description is not detected on the main page of Decodare. 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: