7.4 sec in total
1.8 sec
5.4 sec
169 ms
Visit oapi.int now to see the best up-to-date OAPI content for Cameroon and also check out these interesting facts you probably never knew about oapi.int
Le portail de l'organisation Africaine de la Propriété intellectuelle
Visit oapi.intWe analyzed Oapi.int page load time and found that the first response time was 1.8 sec and then it took 5.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
oapi.int performance score
name
value
score
weighting
Value12.2 s
0/100
10%
Value17.7 s
0/100
25%
Value25.0 s
0/100
10%
Value120 ms
97/100
30%
Value0.148
76/100
15%
Value13.7 s
10/100
10%
1778 ms
382 ms
384 ms
388 ms
583 ms
Our browser made a total of 82 requests to load all elements on the main page. We found that 95% of them (78 requests) were addressed to the original Oapi.int, 2% (2 requests) were made to Google-analytics.com and 1% (1 request) were made to Adobe.com. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Oapi.int.
Page size can be reduced by 49.1 kB (65%)
75.6 kB
26.5 kB
In fact, the total size of Oapi.int main page is 75.6 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. 15% of websites need less resources to load. HTML takes 58.5 kB which makes up the majority of the site volume.
Potential reduce by 49.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 49.1 kB or 84% of the original size.
Potential reduce by 34 B
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 26 (39%)
66
40
The browser has sent 66 CSS, Javascripts, AJAX and image requests in order to completely render the main page of OAPI. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for CSS and as a result speed up the page load time.
oapi.int
1778 ms
shadowbox.css
382 ms
template.css
384 ms
custom.css
388 ms
phocadownload.css
583 ms
style_standard.css
591 ms
style.php
572 ms
mod_yoo_search.css.php
399 ms
mod_jflanguageselection.css
594 ms
mootools-release-1.11.js
1502 ms
jquery-1.4.2.min.js
1513 ms
jquery-noconflict.js
587 ms
jquery-ui-1.8.2.custom.min.js
2005 ms
caption.js
777 ms
base.js
780 ms
accordionmenu.js
803 ms
fancymenu.js
965 ms
dropdownmenu.js
970 ms
template.js
1004 ms
engine_standard_compressed.js
1153 ms
rokslideshow.js
1356 ms
engine_compress.js
1200 ms
importer.php
1357 ms
mod_yoo_search.js
1393 ms
yoo_effects.js.php
1744 ms
reset.css
1354 ms
layout.css
1408 ms
typography.css
1488 ms
menus.css
1505 ms
modules.css
1924 ms
joomla.css
1611 ms
extensions.css
1673 ms
get_flash_player.gif
21 ms
page_bg_t.png
188 ms
toolbar_separator.png
185 ms
menubar_bg.png
377 ms
menubar_shadow.png
191 ms
entete.png
664 ms
menu_level1_item.png
193 ms
menu_dropdown_corners.png
366 ms
menu_dropdown_edges.png
373 ms
menu_level3_item.png
374 ms
searchbox_bg.png
381 ms
magnifier_icon.png
550 ms
close_icon.png
560 ms
couv_OAPImag_26min.jpg
561 ms
revue_africaine.jpg
576 ms
couv_Catalogue_apide_2015min.jpg
580 ms
COUV_CataloqueMaster_2015.jpg
733 ms
guide_magistrat.jpg
751 ms
metier.png
992 ms
0.jpg
1676 ms
1.jpg
1419 ms
Benin.png
851 ms
burkina.png
915 ms
cameroun.png
944 ms
centrafrique.png
1040 ms
comores.png
1100 ms
congo.png
1133 ms
cotedivoire.png
1177 ms
gabon.png
1248 ms
guinee.png
1283 ms
guineebi.png
1322 ms
guineeeq.png
1363 ms
mali.png
1450 ms
mauritanie.png
1467 ms
niger.png
1510 ms
senegal.png
1549 ms
tchad.png
1591 ms
ga.js
8 ms
__utm.gif
13 ms
collect
69 ms
togo.png
1462 ms
content_wrapper_corners.png
1866 ms
breadcrumbs.png
1513 ms
content_wrapper_edges_without.png
1545 ms
module_black.png
1432 ms
module_rounded_grey_header_blue.png
1461 ms
module_rounded_white_corners.png
1491 ms
page_bg_b.png
1513 ms
footer_anchor.png
1538 ms
topmenu_item_bg_white.png
1437 ms
oapi.int 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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
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
oapi.int 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
oapi.int SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
FR
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Oapi.int can be misinterpreted by Google and other search engines. Our service has detected that French is used on the page, and it does not match the claimed English language. Our system also found out that Oapi.int 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.
oapi.int
Open Graph description is not detected on the main page of OAPI. 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: