4.5 sec in total
286 ms
3.5 sec
704 ms
Welcome to repairfuture.net homepage info - get ready to check REPAIR Future best content for Turkey right away, or after learning these important things about repairfuture.net
This project aims to debate the Armenian-Turkish issues by allowing various players in the Turkish, Armenian and Armenian Diaspora civil societies to voice their standpoints.
Visit repairfuture.netWe analyzed Repairfuture.net page load time and found that the first response time was 286 ms and then it took 4.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
repairfuture.net performance score
name
value
score
weighting
Value3.9 s
24/100
10%
Value4.1 s
47/100
25%
Value6.2 s
43/100
10%
Value460 ms
62/100
30%
Value0.001
100/100
15%
Value7.5 s
47/100
10%
286 ms
806 ms
85 ms
168 ms
260 ms
Our browser made a total of 150 requests to load all elements on the main page. We found that 92% of them (138 requests) were addressed to the original Repairfuture.net, 3% (4 requests) were made to Platform.twitter.com and 2% (3 requests) were made to Connect.facebook.net. The less responsive or slowest element that took the longest time to load (806 ms) belongs to the original domain Repairfuture.net.
Page size can be reduced by 546.1 kB (8%)
6.6 MB
6.1 MB
In fact, the total size of Repairfuture.net main page is 6.6 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. 65% of websites need less resources to load. Images take 6.0 MB which makes up the majority of the site volume.
Potential reduce by 97.8 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 24.4 kB, which is 22% 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 97.8 kB or 87% of the original size.
Potential reduce by 86.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. REPAIR Future images are well optimized though.
Potential reduce by 272.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 272.6 kB or 66% of the original size.
Potential reduce by 88.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. Repairfuture.net needs all CSS files to be minified and compressed as it can save up to 88.7 kB or 82% of the original size.
Number of requests can be reduced by 47 (46%)
102
55
The browser has sent 102 CSS, Javascripts, AJAX and image requests in order to completely render the main page of REPAIR Future. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 22 to 1 for CSS and as a result speed up the page load time.
repairfuture.net
286 ms
806 ms
default.css
85 ms
mega.css
168 ms
system.css
260 ms
general.css
247 ms
virtuemart.css
255 ms
template.css
325 ms
fonts.css
254 ms
joomla.css
263 ms
extensions.css
329 ms
layout.css
336 ms
responsive.css
340 ms
template.css
345 ms
extensions.css
346 ms
joomla.css
406 ms
k2.css
411 ms
mega.css
418 ms
modal.css
422 ms
module_default.css
427 ms
style.css
434 ms
jstyle.css
491 ms
template.css
495 ms
mootools-core.js
698 ms
mootools-more.js
740 ms
core.js
507 ms
caption.js
515 ms
modal.js
578 ms
jquery.min.js
30 ms
jquery-noconflict.js
578 ms
default.js
590 ms
script.js
597 ms
global.js
662 ms
acymailing_module.js
661 ms
all.js
28 ms
jscript.js
672 ms
js
70 ms
system.css
422 ms
all.js
33 ms
PhotoArticleSevan2.jpg
287 ms
99.jpg
283 ms
LogoYerkirEurope-pt.jpg
286 ms
LogoRegionRhoneAlpes-pt.jpg
286 ms
Logo3-fran.jpg
286 ms
logo-ambFR-TR-pt.jpg
286 ms
Logo-IF-pt.jpg
354 ms
logo-ambFR-ARM-pt.jpg
353 ms
en.gif
101 ms
fr.gif
100 ms
hy.gif
101 ms
tr.gif
102 ms
PhotoArticleMuslu.jpg
98 ms
PhotoArticleTaline.jpg
167 ms
PhotoArticleUraz.jpg
167 ms
PhotoArticleAliBayramoglu.jpg
167 ms
PhotoArticleDemoyan.jpg
167 ms
PhotoArticleSevanDeyirmenjian.jpg
167 ms
Les%20Armniens%20et%20les%20autres%20Armniens%20en%20Turquie.jpg
244 ms
Hello%20from%20Kurdistan%20.jpg
248 ms
_MIK5687.jpg
246 ms
photoArusYumul.jpg
245 ms
PhotoArticleKalfayanIII.1.jpg
247 ms
Pachas.jpg
245 ms
PhotoArticleAydaErbal1.jpg
318 ms
PhotoArticleSeyhanBayraktar.jpg
321 ms
photo%20Bilgin%20Ayata.jpg
321 ms
Article%20Guven%20Gurkan%20Oztan%20et%20Omer%20Turan.jpg
319 ms
PhotoArticleLilitNegation.jpg
323 ms
PhotoArticleKalfayan2.jpg
322 ms
PhotoArticleSait-1.jpg
396 ms
PhotoArticleTatul.1.jpg
396 ms
PhotoArticleVarhamIII.jpg
397 ms
LilitVardanyanPhotoArticle.jpg
397 ms
1%20Surp%20Giragos%20sous%20plastique.jpg
398 ms
2%20Le%20rve%20dAram.jpg
398 ms
3%20Seymus%20Diken%20la%20voix%20de%20Diyarbakir.jpg
474 ms
4%20zgur%20le%20gardien%20du%20cimetire%20armnien.jpg
475 ms
5%20Comme%20un%20hommage.jpg
476 ms
6%20Armen.jpg
477 ms
7%20Djeuner%20%20Surp%20Giragos.jpg
478 ms
8%20Chez%20Sarkis%20et%20Bayzar.jpg
478 ms
all.js
14 ms
9%20Le%20pont%20de%20la%20mort%20ou%20presque.jpg
538 ms
54 ms
widgets.js
15 ms
PhotoArticleMuslu.jpg
242 ms
10%20Retour%20%20lcole.jpg
455 ms
11%20Exploitation.jpg
456 ms
12%20Mustafa%20and%20akir.jpg
456 ms
Voces-Regular.woff
84 ms
widget_iframe.2f70fb173b9000da126c79afe2098f02.html
17 ms
settings
98 ms
PhotoArticleUraz2.jpg
164 ms
PhotoArticleSevanDeyirmenjian.jpg
241 ms
PhotoArticleUraz.jpg
324 ms
PhotoArticleDemoyan.jpg
166 ms
PhotoArticleTaline.jpg
114 ms
PhotoArticleAliBayramoglu.jpg
188 ms
13%20Yedvart%20Tomasyan.jpg
365 ms
button.856debeac157d9669cf51e73a08fbc93.js
2 ms
Les%20Armniens%20et%20les%20autres%20Armniens%20en%20Turquie.jpg
244 ms
_MIK5687.jpg
248 ms
Pachas.jpg
178 ms
photoArusYumul.jpg
193 ms
Hello%20from%20Kurdistan%20.jpg
319 ms
PhotoArticleKalfayanIII.1.jpg
336 ms
embeds
36 ms
follow_button.2f70fb173b9000da126c79afe2098f02.en-gb.html
24 ms
99.jpg
484 ms
LogoRegionRhoneAlpes-pt.jpg
347 ms
LogoYerkirEurope-pt.jpg
353 ms
PhotoArticleSevan2.jpg
742 ms
logo-ambFR-TR-pt.jpg
436 ms
Logo3-fran.jpg
358 ms
14%20Pourquoi%20pas%20.jpg
272 ms
PhotoArticleAydaErbal1.jpg
203 ms
Article%20Guven%20Gurkan%20Oztan%20et%20Omer%20Turan.jpg
332 ms
photo%20Bilgin%20Ayata.jpg
329 ms
PhotoArticleSeyhanBayraktar.jpg
255 ms
PhotoArticleKalfayan2.jpg
285 ms
PhotoArticleLilitNegation.jpg
403 ms
icon-search.png
335 ms
logo.png
343 ms
icon_home_hover.png
353 ms
logo-ambFR-ARM-pt.jpg
359 ms
Logo-IF-pt.jpg
366 ms
arrow-submenu.png
380 ms
PhotoArticleSait-1.jpg
337 ms
PhotoArticleTatul.1.jpg
346 ms
LilitVardanyanPhotoArticle.jpg
362 ms
PhotoArticleVarhamIII.jpg
378 ms
1%20Surp%20Giragos%20sous%20plastique.jpg
488 ms
2%20Le%20rve%20dAram.jpg
498 ms
icon-style.png
412 ms
bg-nav.png
403 ms
undefined
643 ms
3%20Seymus%20Diken%20la%20voix%20de%20Diyarbakir.jpg
462 ms
4%20zgur%20le%20gardien%20du%20cimetire%20armnien.jpg
503 ms
5%20Comme%20un%20hommage.jpg
521 ms
6%20Armen.jpg
494 ms
7%20Djeuner%20%20Surp%20Giragos.jpg
506 ms
8%20Chez%20Sarkis%20et%20Bayzar.jpg
543 ms
black.png
569 ms
border.png
573 ms
9%20Le%20pont%20de%20la%20mort%20ou%20presque.jpg
515 ms
10%20Retour%20%20lcole.jpg
529 ms
11%20Exploitation.jpg
553 ms
12%20Mustafa%20and%20akir.jpg
586 ms
13%20Yedvart%20Tomasyan.jpg
593 ms
14%20Pourquoi%20pas%20.jpg
601 ms
repairfuture.net 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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Form elements do not have associated labels
Links do not have a discernible name
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.
repairfuture.net 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
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
repairfuture.net 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 doesn't use legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Repairfuture.net 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 Repairfuture.net 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.
repairfuture.net
Open Graph description is not detected on the main page of REPAIR Future. 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: