3.1 sec in total
316 ms
2.6 sec
182 ms
Visit nafo.int now to see the best up-to-date Nafo content for Indonesia and also check out these interesting facts you probably never knew about nafo.int
NAFO's objective is to ensure long term conservation and sustainable use of the fishery resources in the Convention Area and, in so doing, to safeguard the marine ecosystems in which these resourc...
Visit nafo.intWe analyzed Nafo.int page load time and found that the first response time was 316 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
nafo.int performance score
name
value
score
weighting
Value28.3 s
0/100
10%
Value37.2 s
0/100
25%
Value28.3 s
0/100
10%
Value1,360 ms
16/100
30%
Value0.1
90/100
15%
Value37.9 s
0/100
10%
316 ms
373 ms
494 ms
88 ms
123 ms
Our browser made a total of 101 requests to load all elements on the main page. We found that 72% of them (73 requests) were addressed to the original Nafo.int, 13% (13 requests) were made to Fonts.gstatic.com and 5% (5 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (966 ms) belongs to the original domain Nafo.int.
Page size can be reduced by 200.2 kB (3%)
6.3 MB
6.1 MB
In fact, the total size of Nafo.int main page is 6.3 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. 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 3.9 MB which makes up the majority of the site volume.
Potential reduce by 61.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. 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 61.7 kB or 82% of the original size.
Potential reduce by 75.1 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. Nafo images are well optimized though.
Potential reduce by 15.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. This website has mostly compressed JavaScripts.
Potential reduce by 47.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. Nafo.int has all CSS files already compressed.
Number of requests can be reduced by 44 (52%)
84
40
The browser has sent 84 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Nafo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and from 22 to 1 for CSS and as a result speed up the page load time.
nafo.int
316 ms
nafo.int
373 ms
www.nafo.int
494 ms
js
88 ms
ej2.min.js
123 ms
lz-string.min.js
39 ms
bootstrap4.css
56 ms
bootstrap.min.css
45 ms
default.css
30 ms
bootstrap.min.css
66 ms
all.min.css
105 ms
base.css
815 ms
sdi8g6oiu3m.css
822 ms
skin.css
823 ms
Vision.css
823 ms
blue.css
829 ms
container.css
831 ms
container.css
832 ms
portal.css
834 ms
multislider.css
869 ms
rateit.css
863 ms
Theme1.css
869 ms
common.css
866 ms
eds_jq.js
889 ms
eds_jq.js
870 ms
jquery.js
915 ms
jquery-ui.min.js
945 ms
js
818 ms
WebResource.axd
895 ms
ScriptResource.axd
916 ms
ScriptResource.axd
896 ms
dnn.modalpopup.js
914 ms
bootstrap.bundle.min.js
923 ms
main-scripts.js
924 ms
dnncore.js
940 ms
eds_easing.1.3.js
942 ms
jquery.rateit_2.2.js
943 ms
multislider.2.51.2.min.js
953 ms
EasyDnnSolutions_1.1_2.2.js
951 ms
edsAccordion-1.1.js
966 ms
font-awesome.min.css
151 ms
font-awesome.min.css
105 ms
custom.css
107 ms
gtm.js
69 ms
NAFO-LOGO-v2.png
38 ms
mvnjb5gc.jpg
131 ms
sxiknjhc.jpg
131 ms
1ig0lm3b.jpg
39 ms
1nwyah2y.jpg
130 ms
j1t525wg.jpg
130 ms
2ofqdkq0.jpg
131 ms
biy3gxch.jpg
131 ms
rt0e40bc.jpg
138 ms
1fissi2c.jpg
138 ms
l1yj3aq1.jpg
137 ms
ojgemzbw.jpg
137 ms
vnlft1ei.jpg
137 ms
ealncs2e.jpg
138 ms
dhmbt1kq.jpg
196 ms
Poster-EAFM-symposium-2025-web.jpg
196 ms
flags-web-01.svg
193 ms
flags-web-02.svg
181 ms
cse.js
103 ms
NAFO-banner_1.png
161 ms
raMenuTriggerIcon.png
157 ms
black-gradient.png
207 ms
loading-custom.gif
167 ms
y7lebkjgREBJK96VQi37ZtIh4imgI8P11RFo6YPCPC0.woff
101 ms
BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjojISmYWRl.woff
101 ms
BngMUXZYTXPIvIBgJJSb6ufD5qM.woff
177 ms
dazS1PrQQuCxC3iOAJFEJYUt79146ZFaIJxILcpzmhI.woff
130 ms
BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjoa4OmYWRl.woff
131 ms
BngRUXZYTXPIvIBgJJSb6u92w7CIwRs.woff
258 ms
ahcbv8612zF4jxrwMosbXsly.woff
176 ms
AVs3lMmyGvSpQmMt6DeeRj8E0i7KZn-EPnyo3HZu7kw.woff
130 ms
ahcbv8612zF4jxrwMosbXsly.woff
130 ms
ahcev8612zF4jxrwMosT--thjGy7.woff
259 ms
ahcev8612zF4jxrwMosT6-xhjGy7.woff
131 ms
qZpi6ZVZg3L2RL_xoBLxWRa1RVmPjeKy21_GQJaLlJI.woff
137 ms
ahcev8612zF4jxrwMosT6-xhjGy7.woff
137 ms
rss.png
114 ms
light-skin-1.png
104 ms
glyphicons-halflings-regular.woff
65 ms
time-blue.png
110 ms
gradient.png
108 ms
cse_element__en.js
46 ms
default+en.css
64 ms
default.css
66 ms
expand-blue.png
61 ms
async-ads.js
56 ms
branding.png
53 ms
background_image_fractallines2_dark.png
104 ms
bottom-content-shadow.png
103 ms
facebook.png
103 ms
twitter.png
103 ms
linkedin.png
103 ms
footer-bg.png
103 ms
top-link-green.png
107 ms
top-link-arrow-green.png
106 ms
backToTopBg.png
109 ms
clear.png
102 ms
nafo.int 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
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.
nafo.int best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
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
Missing source maps for large first-party JavaScript
nafo.int 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
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 Nafo.int 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 Nafo.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.
nafo.int
Open Graph description is not detected on the main page of Nafo. 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: