6.7 sec in total
2 sec
4 sec
665 ms
Visit doubleteam.gr now to see the best up-to-date Double Team content for Greece and also check out these interesting facts you probably never knew about doubleteam.gr
παγίδες στις γωνίες...
Visit doubleteam.grWe analyzed Doubleteam.gr page load time and found that the first response time was 2 sec and then it took 4.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
doubleteam.gr performance score
name
value
score
weighting
Value3.0 s
50/100
10%
Value3.4 s
66/100
25%
Value5.1 s
61/100
10%
Value1,300 ms
18/100
30%
Value0.105
88/100
15%
Value14.5 s
8/100
10%
2035 ms
242 ms
176 ms
205 ms
151 ms
Our browser made a total of 101 requests to load all elements on the main page. We found that 23% of them (23 requests) were addressed to the original Doubleteam.gr, 13% (13 requests) were made to Static.xx.fbcdn.net and 6% (6 requests) were made to Googleads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Doubleteam.gr.
Page size can be reduced by 494.2 kB (51%)
966.1 kB
471.9 kB
In fact, the total size of Doubleteam.gr main page is 966.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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 384.7 kB which makes up the majority of the site volume.
Potential reduce by 115.0 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 115.0 kB or 76% of the original size.
Potential reduce by 4.8 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. Double Team images are well optimized though.
Potential reduce by 189.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 189.6 kB or 49% of the original size.
Potential reduce by 184.7 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. Doubleteam.gr needs all CSS files to be minified and compressed as it can save up to 184.7 kB or 85% of the original size.
Number of requests can be reduced by 66 (69%)
95
29
The browser has sent 95 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Double Team. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 40 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.
doubleteam.gr
2035 ms
wp-emoji-release.min.js
242 ms
bbpress.css
176 ms
shortcodes.css
205 ms
style.css
151 ms
media-queries.css
172 ms
prettyPhoto.css
210 ms
css
27 ms
styles.css
260 ms
magnific-popup.css
275 ms
jetpack.css
288 ms
jquery.js
453 ms
jquery-migrate.min.js
285 ms
audio-player.js
322 ms
adsbygoogle.js
10 ms
8119171.js
62 ms
survey.js
57 ms
cleantalk_nocache.js
261 ms
photon.js
276 ms
jquery.t-countdown.js
278 ms
devicepx-jetpack.js
6 ms
gprofiles.js
55 ms
wpgroho.js
279 ms
jquery.prettyPhoto.js
320 ms
carousel.js
471 ms
themify.script.js
349 ms
wp-embed.min.js
348 ms
e-201611.js
3 ms
ga.js
6 ms
__utm.gif
38 ms
collect
56 ms
ga-audiences
138 ms
%CF%83%CE%AC%CE%BB%CE%B5.jpg
825 ms
b4b93bb8807b6a1dcc827facd4346838_L.jpg
835 ms
8b773d7b6e796c40fe1926a9685a96f7
63 ms
7374bbf804f1455361ca92ee7afeacbb
76 ms
97c38cd52e16d9adf47b061955aecc7c
76 ms
7374bbf804f1455361ca92ee7afeacbb
223 ms
e7bf781676ef0703139d2485c1138ab6
127 ms
8b773d7b6e796c40fe1926a9685a96f7
263 ms
cap.jpg
306 ms
icon-post.png
262 ms
white-grad.png
51 ms
9ZZVVBRCceNnPBXqWLH8IBaCi8XR2Wndwbau3-eaE1g.ttf
44 ms
4zlbkWdiblhTyAxV3yYOK1Map0k-03pf3IKr-TpLv1-glnMp3_3A8V8Ai8YosRtX.ttf
80 ms
ca-pub-6353975002436850.js
211 ms
zrt_lookup.html
209 ms
show_ads_impl.js
68 ms
sdk.js
60 ms
186 ms
177 ms
widgets.js
148 ms
ads
596 ms
osd.js
47 ms
136 ms
jsc_1446473975.js
45 ms
121 ms
xd_arbiter.php
32 ms
xd_arbiter.php
63 ms
ads
460 ms
ads
427 ms
ads
404 ms
9340188.js
56 ms
hovercard.css
89 ms
services.css
96 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
138 ms
m_js_controller.js
167 ms
abg.js
184 ms
googlelogo_color_112x36dp.png
205 ms
5431221881935096000
166 ms
g.gif
123 ms
tweet_button.html
69 ms
jot
326 ms
296172728199823360
419 ms
syndication
299 ms
favicon
118 ms
nessie_icon_tiamat_white.png
108 ms
page.php
230 ms
s
70 ms
x_button_blue2.png
48 ms
like.php
154 ms
fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js
14 ms
LUdypCgtRlc.css
58 ms
q68gy-v_YMF.js
54 ms
YvxwM8R7ol8.js
83 ms
ihptErjAmMX.js
53 ms
qeKvIRsJabD.js
154 ms
LVx-xkvaJ0b.png
42 ms
qeKvIRsJabD.js
108 ms
12650868_1559266411060588_7490716665656925408_n.jpg
110 ms
12644687_1559266757727220_1171150558462116675_n.jpg
83 ms
wL6VQj7Ab77.png
61 ms
s7jcwEQH7Sx.png
58 ms
proxy.jpg
77 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
4 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
11 ms
R9a_DtVRZgv.js
23 ms
cUDgRFxaoIk.js
23 ms
0JBr1QHp8Gi.js
23 ms
kDOzhTr2W91.js
24 ms
ui
21 ms
doubleteam.gr 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
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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.
doubleteam.gr best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
doubleteam.gr SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
EL
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Doubleteam.gr can be misinterpreted by Google and other search engines. Our service has detected that Greek is used on the page, and it does not match the claimed English language. Our system also found out that Doubleteam.gr 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.
doubleteam.gr
Open Graph data is detected on the main page of Double Team. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: