6.8 sec in total
419 ms
6 sec
376 ms
Welcome to otr.tg homepage info - get ready to check Otr best content for Togo right away, or after learning these important things about otr.tg
Site officiel de l'Office Togolais des Recettes
Visit otr.tgWe analyzed Otr.tg page load time and found that the first response time was 419 ms and then it took 6.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
otr.tg performance score
name
value
score
weighting
Value10.9 s
0/100
10%
Value12.2 s
0/100
25%
Value16.4 s
0/100
10%
Value700 ms
42/100
30%
Value0.144
78/100
15%
Value19.1 s
2/100
10%
419 ms
2507 ms
80 ms
160 ms
239 ms
Our browser made a total of 123 requests to load all elements on the main page. We found that 82% of them (101 requests) were addressed to the original Otr.tg, 11% (13 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Otr.tg.
Page size can be reduced by 1.8 MB (44%)
4.0 MB
2.3 MB
In fact, the total size of Otr.tg main page is 4.0 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. 75% 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. Images take 2.7 MB which makes up the majority of the site volume.
Potential reduce by 109.7 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.8 kB, which is 19% 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 109.7 kB or 82% of the original size.
Potential reduce by 777.5 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. Obviously, Otr needs image optimization as it can save up to 777.5 kB or 29% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 463.9 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 463.9 kB or 62% of the original size.
Potential reduce by 410.5 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. Otr.tg needs all CSS files to be minified and compressed as it can save up to 410.5 kB or 85% of the original size.
Number of requests can be reduced by 52 (50%)
105
53
The browser has sent 105 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Otr. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 36 to 1 for JavaScripts and from 18 to 1 for CSS and as a result speed up the page load time.
otr.tg
419 ms
2507 ms
style.css
80 ms
template.css
160 ms
jcemediabox.css
239 ms
style.css
240 ms
layout.css
241 ms
jquery.fancybox.css
241 ms
jquery.fancybox-buttons.css
245 ms
jquery.fancybox-thumbs.css
251 ms
template.css
713 ms
lrstyle.css
318 ms
mod_otclientlogosscroller.css
319 ms
module.css
559 ms
mod_news_show_sp2.css
326 ms
style.css
334 ms
camera.css
396 ms
multi-col.css
397 ms
plusone.js
24 ms
mootools-core.js
570 ms
core.js
416 ms
jquery.min.js
633 ms
jquery-noconflict.js
476 ms
jquery-migrate.min.js
500 ms
caption.js
556 ms
jcemediabox.js
668 ms
bootstrap.min.js
756 ms
acymailing_module.js
636 ms
jdownloadurl.js
650 ms
extrawatch.js
755 ms
heatmap.js
760 ms
fcfc.js
761 ms
koowa.kquery.js
762 ms
sp_highlighter.js
789 ms
camera.min.js
791 ms
css
34 ms
css
54 ms
jquery.carousel.js
830 ms
jquery.centerIn.js
830 ms
jquery.modernizr.min.js
831 ms
jquery.stellar.min.js
833 ms
jquery.simplr.smoothscroll.min.js
870 ms
jquery.BlackAndWhite.min.js
792 ms
jquery.fancybox.pack.js
713 ms
jquery.fancybox-buttons.js
712 ms
jquery.fancybox-media.js
711 ms
jquery.fancybox-thumbs.js
711 ms
jquery.pep.js
860 ms
jquery.vide.min.js
854 ms
scripts.js
789 ms
cb=gapi.loaded_0
30 ms
fond.gif
294 ms
nav-bg.png
292 ms
logo.png
294 ms
showcaseBg.jpg
323 ms
IMG_8541_400x225.jpg
526 ms
IMG_9906_125x70.jpg
295 ms
Afritac-1_125x70.jpg
323 ms
_DSC6088_125x70.JPG
324 ms
pk_tchodie_2020.jpg
467 ms
fraude.jpg
466 ms
lome_port_7j_7.jpg
467 ms
num_vert.jpg
466 ms
adoptons_la_facture_normalisee.jpg
465 ms
sensibilisation_fiscale.jpg
526 ms
quittance_securisee.jpg
526 ms
e-paiement.jpg
530 ms
e-paiement2.jpg
527 ms
legis_down_2.png
624 ms
encart_doc_fiscaux.png
624 ms
partner_mef.png
622 ms
partner_bad.png
623 ms
partner_seguce.png
622 ms
partner_bm.png
607 ms
partner_omc.png
663 ms
partner_omd.png
662 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
114 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
113 ms
KFOlCnqEu92Fr1MmSU5fBBc9.ttf
143 ms
KFOkCnqEu92Fr1MmgVxIIzc.ttf
144 ms
KFOlCnqEu92Fr1MmWUlfBBc9.ttf
144 ms
KFOlCnqEu92Fr1MmYUtfBBc9.ttf
144 ms
fontawesome-webfont.woff
663 ms
partner_ecowas.png
654 ms
KFOkCnqEu92Fr1Mu51xIIzc.ttf
135 ms
KFOjCnqEu92Fr1Mu51S7ACc6CsE.ttf
135 ms
KFOjCnqEu92Fr1Mu51TjASc6CsE.ttf
136 ms
KFOiCnqEu92Fr1Mu51QrEzAdKg.ttf
256 ms
KFOjCnqEu92Fr1Mu51TzBic6CsE.ttf
255 ms
KFOjCnqEu92Fr1Mu51TLBCc6CsE.ttf
135 ms
Ycm2sZJORluHnXbIfmlR-A.ttf
242 ms
all.js
206 ms
koowa.ttf
562 ms
agent.js
584 ms
partner_ataf.png
628 ms
partner_uemoa.png
628 ms
partner_credaf.png
629 ms
partner_ccit.png
603 ms
partner_fmi.png
481 ms
partner_port.png
491 ms
partner_cfe_tg.png
552 ms
style3.png
552 ms
borderBg.png
554 ms
more.png
560 ms
whiteshadowBg.png
561 ms
all.js
123 ms
carousel_control.png
544 ms
analytics.js
136 ms
popup.html
484 ms
tooltip.html
482 ms
pagination.png
462 ms
camera-loader.gif
464 ms
camera_caption.png
469 ms
Slide-56-dprciation-2024.png
817 ms
video.gif
618 ms
collect
13 ms
js
68 ms
video.jpg
480 ms
video.jpeg
481 ms
video.png
645 ms
camera_caption_inner.png
488 ms
210 ms
slide-51.jpg
82 ms
otr.tg 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
Image elements do not have [alt] attributes
Links do not have a discernible name
<object> elements do not have alternate text
otr.tg 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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
otr.tg SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
Document uses plugins
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
![]()
FR
![]()
FR
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Otr.tg can be misinterpreted by Google and other search engines. Our service has detected that French is used on the page, and it matches the claimed language. Our system also found out that Otr.tg 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.
otr.tg
Open Graph description is not detected on the main page of Otr. 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: