1.5 sec in total
177 ms
1.1 sec
200 ms
Click here to check amazing DOUBLEYE content. Otherwise, check out these important facts you probably never knew about doubleye.com
THE HAPPY TOOTH
Visit doubleye.comWe analyzed Doubleye.com page load time and found that the first response time was 177 ms and then it took 1.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.
doubleye.com performance score
name
value
score
weighting
Value3.8 s
26/100
10%
Value7.4 s
4/100
25%
Value8.3 s
19/100
10%
Value480 ms
60/100
30%
Value0.563
12/100
15%
Value13.6 s
11/100
10%
177 ms
33 ms
26 ms
113 ms
23 ms
Our browser made a total of 37 requests to load all elements on the main page. We found that 5% of them (2 requests) were addressed to the original Doubleye.com, 24% (9 requests) were made to Fonts.gstatic.com and 22% (8 requests) were made to Gstatic.com. The less responsive or slowest element that took the longest time to load (573 ms) relates to the external source Lh3.googleusercontent.com.
Page size can be reduced by 169.9 kB (10%)
1.7 MB
1.5 MB
In fact, the total size of Doubleye.com main page is 1.7 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. 55% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 79.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 79.2 kB or 82% 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.4 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.
www.doubleye.com
177 ms
css
33 ms
css
26 ms
rs=AGEqA5mM8dLN5jAk-iolKw1LqHInNYaCsw
113 ms
client.js
23 ms
js
66 ms
m=view
28 ms
cb=gapi.loaded_0
191 ms
YN3EIX7LWqA-e57JIU9viHLdFkr6uMFv711x7ZByaUnhD2MZCWvFCVTDHVaHJj1bRLR8U7pMX01qx1wA0HRJOp4=w16383
573 ms
ztRA-xT5UrmIWLVobzaJehUCEfhoUFRT4OO9yLTvnnfiYtVWqFJ1kH75yJ0qxOZacda_ocvdp1RxfQwh1AYblSmuYbSoYRWmPf3znGPUs5KjiUAu0xCdgylK7DCLWbkIbw=w1280
572 ms
foREOkTCLxycdyPN3lOtcyTQWWEZHcYCwn2y7f2erYFsLSZZfU2yE8ec7ldrIGZwUWJc4u2jiewn8lRyZ9Do1xdbLLaHjhoxYfskEeDRtX4Gsbu9Yu_PYHqpnYrjo3HcTQ=w1280
568 ms
Au1LraRVQgPyxRLbG7A2OchQ5FxnVdDdVFSjAevWRhvGd85x2veiWNRBtB1Ku052sFJ2f16WfMpRVfQ7PybnTR2tCI0r6Bfzb4-1YXS8M3r4nN2jTjYwpX-XzRsibnmp3Q=w1280
570 ms
facebook_colored_44dp.png
325 ms
m=sy1j,sy1l,sy1m,sy1k,FoQBg
159 ms
m=sy38,TRvtze
159 ms
Krt2sxDL0Rjn1bgoNFaKaHedrClAdhZYvE_8yxyioXbLH9ALro0KE1OGVMOnwKuBxDxelCKYmKRm9rQwVbTCx2cGtI94DCaQkQqa2M0H0W3qlkoml33kvVY101aGPNkeKA=w1280
400 ms
instagram_colored_44dp.png
211 ms
LyHUQ5-_NoYXOIfutIPAfcVRguq8jHsFK8G5RgimtHFw6HOrE3A3L5eeLc9FViviwdynFzRUrQEwFiWkw_jdclqj5CJDJwxuvoA_E1zPeCNbNbCgEP1BdTyeOKYzU2-NDg=w1280
457 ms
gEx6U0kraVcrtvdX3VWy4vjIts9uqEgqx9XVzddZ6idqrIhLnxw8uIui6gHGom756UKPMro4WtFacPsKvno-tw02FH5sOZ_eQI_H0JOqCfDi0KzpaaXVopQjSPla0WU9Eg=w1280
400 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
298 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
298 ms
KFOlCnqEu92Fr1MmSU5fBBc9.ttf
381 ms
KFOlCnqEu92Fr1MmWUlfBBc9.ttf
405 ms
E21x_cfngu7HiRpPX3ZpNE4kY5zKSPmJXkF0VDD2RAqnS43rvdw.ttf
417 ms
E21x_cfngu7HiRpPX3ZpNE4kY5zKSPmJXkF0VDD2RAp5TI3rvdw.ttf
416 ms
E21x_cfngu7HiRpPX3ZpNE4kY5zKSPmJXkF0VDD2RApATI3rvdw.ttf
418 ms
4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrw2IJllpyw.ttf
416 ms
4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrwEIJllpyw.ttf
416 ms
m=MpJwZc,n73qwf,A4UTCb,mzzZzc,CHCSlb,qAKInc,sy14,YXyON,sy39,abQiW,sy12,PVlQOd,NPKaK,sy7,BVgquf,fmklff,TGYpv,KUM7Z,qEW1W,oNFsLb,sy45,yxTchf,sy46,sy47,xQtZb,yf2Bs,sy3,sya,yyxWAc,qddgKe,sy3b,SM1lmd,sy9,sy8,sy13,RRzQxe,sy15,YV8yqd,sy2,syl,sym,syc,sy2j,sy4,syb,fNFZH,sy3a,syn,RrXLpc,cgRV2c,sy23,o1L5Wb,X4BaPc,syg,sy1d,Md9ENb
162 ms
m=sy34,IZT63,vfuNJf,sy3t,sy3x,sy3z,sy48,sy49,sy4a,siKnQd,sy1a,sy3r,sy3y,sy40,sy35,YNjGDd,sy41,PrPYRd,iFQyKf,hc6Ubd,sy4b,SpsfSb,sy3u,sy3w,wR5FRb,pXdRYb,dIoSBb,zbML3c
132 ms
js
130 ms
js
236 ms
analytics.js
314 ms
m=NTMZac,m9oV,rCcCxc,RAnnUd,sy10,sy33,gJzDyc,sy3c,uu7UOe,sy3d,soHxf,sy3e,uY3Nvd,syx,syw,sy2x,HYv29e
91 ms
m=sy18,sy1f,sy19,sy1b,sy1c,sy1e,fuVYe,vVEdxc,sy1g,sy1h,sy1i,CG0Qwb
135 ms
logImpressions
213 ms
collect
33 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: