1.8 sec in total
70 ms
1.5 sec
232 ms
Click here to check amazing DOUBLEYE content. Otherwise, check out these important facts you probably never knew about doubleye.com
SIGN
Visit doubleye.comWe analyzed Doubleye.com page load time and found that the first response time was 70 ms and then it took 1.7 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
doubleye.com performance score
name
value
score
weighting
Value3.7 s
29/100
10%
Value14.7 s
0/100
25%
Value8.1 s
21/100
10%
Value1,660 ms
11/100
30%
Value0.864
4/100
15%
Value13.5 s
11/100
10%
70 ms
150 ms
45 ms
57 ms
450 ms
Our browser made a total of 38 requests to load all elements on the main page. We found that 8% of them (3 requests) were addressed to the original Doubleye.com, 24% (9 requests) were made to Fonts.gstatic.com and 21% (8 requests) were made to Gstatic.com. The less responsive or slowest element that took the longest time to load (661 ms) relates to the external source Lh6.googleusercontent.com.
Page size can be reduced by 169.0 kB (9%)
1.8 MB
1.6 MB
In fact, the total size of Doubleye.com main page is 1.8 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. 60% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.
Potential reduce by 78.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. 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 78.1 kB or 83% of the original size.
Potential reduce by 89.3 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. DOUBLEYE images are well optimized though.
Potential reduce by 1.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. This website has mostly compressed JavaScripts.
Number of requests can be reduced by 12 (44%)
27
15
The browser has sent 27 CSS, Javascripts, AJAX and image requests in order to completely render the main page of DOUBLEYE. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and as a result speed up the page load time.
doubleye.com
70 ms
www.doubleye.com
150 ms
css
45 ms
css
57 ms
rs=AGEqA5l_OFskOjz4Uq-W-NY4XLlIZzmdVw
450 ms
client.js
41 ms
js
69 ms
m=view
35 ms
cb=gapi.loaded_0
196 ms
yJQqgr2VTPpy_9xxHvrvoNq0FKkgDjHqnhisZOEJ5oByc4XBvOXKyrS76BO7XfLVsXJRQlbm_v5Yk_UXpCMXxR4=w16383
353 ms
7sKrQxVY7sTDO_hdWF1gHMETB0bjI9W-U0JcLGy-k-fvOXXHbyT248z6lY0POr7ANqpGBrY3Sb_MWjJc6C1ay9F-9UtdzxSurmkbfD6EZqyZFRtP2VnwQ3W59mMj5m3Frg=w1280
527 ms
Qf2tFzE7Cf6hM8HIoTZZ-XYWLdwJ_3laQSh0aZcJBOhfZ6be2M_pAi7X0J9p12glVlf4lSxtHTJpi214O4Ojusi2hlHQtdH0xpJVU_NEZq3m_zdhl8rswbE_-RS4flrUsw=w1280
530 ms
nLjovP0iz0QypZ4o6hl3gwg0WmyblvG4hCgiqjghA4q4krN4JHCunkQXraUfuig2Qvl6VUdiUOYnXbx8P9PBDKFTfPOXPJI5d-hKlEJLemof-gIx8yAOPu7-OY-zroHMdA=w1280
539 ms
facebook_colored_44dp.png
331 ms
biF5tP5sfp7VUYx_R29Pv23I2tsW2bt9s1HRWy59qMoKzQCHWploor0y9gbYSUnd6WA17lakJ_6WcWi_XE04bPcVr6uPEQ3butua8mQrpimKtGgGI_rD09s8JLaGNizSLw=w1280
621 ms
IKllJSJoEz9wKCnaO6CWn_Zn7J5pCgdhyGhAOFgZkt2O1XZf5iZVVptbljb-i7n2_IEZJutJEAh_akS_dsaQfTxh3gJWLqlzK4h8yIpOGsXgrCtTcRJU-QXdIApXflooxg=w1280
630 ms
instagram_colored_44dp.png
405 ms
qP_1s09z0VpyoqOGsJ8btxtZU2dr7mkTEyW4zDj4FvB6PLFrANHqocYaYjJd4fudC-ysd_JZ5ZkulJx4loqKhKcA5ms6jBkneFC2pJwTDAJxRN7Xjv1CNX6vafc0y7O1jw=w1280
661 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
382 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
411 ms
KFOlCnqEu92Fr1MmSU5fBBc9.ttf
488 ms
KFOlCnqEu92Fr1MmWUlfBBc9.ttf
501 ms
m=sy19,sy1a,sy18,FoQBg
117 ms
m=sy2t,TRvtze
118 ms
m=MpJwZc,n73qwf,A4UTCb,mzzZzc,CHCSlb,qAKInc,syz,YXyON,sy2u,abQiW,syx,PVlQOd,NPKaK,sy5,BVgquf,fmklff,TGYpv,KUM7Z,qEW1W,oNFsLb,sy3t,yxTchf,sy3u,sy3v,xQtZb,yf2Bs,sy2,sy9,yyxWAc,qddgKe,sy2w,SM1lmd,sy7,sy6,syy,RRzQxe,sy10,YV8yqd,sy8,syb,syl,sya,fNFZH,sy2v,sym,RrXLpc,cgRV2c,sy1m,o1L5Wb,X4BaPc,syg,sy16,Md9ENb
145 ms
m=sy3k,IZT63,vfuNJf,sy3e,sy3i,sy3l,sy3y,sy3w,sy3x,siKnQd,sy3c,sy3j,sy3n,YNjGDd,sy3m,sy3o,PrPYRd,iFQyKf,hc6Ubd,sy3z,SpsfSb,sy3f,sy3h,wR5FRb,pXdRYb,dIoSBb,zbML3c
119 ms
js
114 ms
js
220 ms
analytics.js
172 ms
E21x_cfngu7HiRpPX3ZpNE4kY5zKSPmJXkF0VDD2RAp5TI3rvdw.ttf
408 ms
E21x_cfngu7HiRpPX3ZpNE4kY5zKSPmJXkF0VDD2RApATI3rvdw.ttf
314 ms
E21x_cfngu7HiRpPX3ZpNE4kY5zKSPmJXkF0VDD2RAqnS43rvdw.ttf
309 ms
4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrw2IJllpyw.ttf
290 ms
4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrwEIJllpyw.ttf
289 ms
m=m9oV,sy3p,NTMZac,rCcCxc,RAnnUd,sy2x,sy2y,uu7UOe,nAFL3,sy2q,gJzDyc,sy2z,soHxf,syu,syt,HYv29e,sy30,uY3Nvd
76 ms
m=sy13,sy14,sy15,fuVYe,vVEdxc,sy17,CG0Qwb
100 ms
logImpressions
126 ms
collect
98 ms
doubleye.com accessibility score
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
Image elements do not have [alt] attributes
Links do not have a discernible name
doubleye.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
doubleye.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Doubleye.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Doubleye.com 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.
doubleye.com
Open Graph data is detected on the main page of DOUBLEYE. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: