3.9 sec in total
111 ms
3.6 sec
216 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 111 ms and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
nafo.int performance score
name
value
score
weighting
Value28.7 s
0/100
10%
Value33.8 s
0/100
25%
Value28.7 s
0/100
10%
Value2,080 ms
7/100
30%
Value0.1
90/100
15%
Value41.5 s
0/100
10%
111 ms
117 ms
352 ms
121 ms
194 ms
Our browser made a total of 112 requests to load all elements on the main page. We found that 76% of them (85 requests) were addressed to the original Nafo.int, 13% (15 requests) were made to Fonts.gstatic.com and 3% (3 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.5 sec) relates to the external source Googletagmanager.com.
Page size can be reduced by 355.0 kB (8%)
4.4 MB
4.1 MB
In fact, the total size of Nafo.int main page is 4.4 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. 85% 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 3.6 MB which makes up the majority of the site volume.
Potential reduce by 65.2 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 65.2 kB or 83% of the original size.
Potential reduce by 213.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 61.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 61.9 kB or 21% of the original size.
Potential reduce by 14.9 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 43 (46%)
93
50
The browser has sent 93 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 23 to 1 for JavaScripts and from 22 to 1 for CSS and as a result speed up the page load time.
nafo.int
111 ms
nafo.int
117 ms
www.nafo.int
352 ms
gtm.js
121 ms
ej2.min.js
194 ms
lz-string.min.js
62 ms
bootstrap4.css
85 ms
bootstrap.min.css
59 ms
default.css
83 ms
bootstrap.min.css
144 ms
all.min.css
147 ms
base.css
173 ms
sdi8g6oiu3m.css
147 ms
skin.css
176 ms
Vision.css
1450 ms
blue.css
183 ms
container.css
178 ms
container.css
179 ms
portal.css
1448 ms
multislider.css
1462 ms
rateit.css
1449 ms
Theme1.css
1464 ms
common.css
1466 ms
eds_jq.js
1473 ms
eds_jq.js
1475 ms
jquery.js
1470 ms
jquery-ui.js
1477 ms
js
1482 ms
WebResource.axd
1467 ms
ScriptResource.axd
1468 ms
ScriptResource.axd
1470 ms
dnn.modalpopup.js
1471 ms
bootstrap.bundle.min.js
1473 ms
main-scripts.js
1472 ms
dnncore.js
1473 ms
eds_easing.1.3.js
1475 ms
jquery.rateit_2.2.js
1476 ms
multislider.2.51.2.min.js
1477 ms
EasyDnnSolutions_1.1_2.2.js
1475 ms
edsAccordion-1.1.js
1475 ms
font-awesome.min.css
38 ms
custom.css
29 ms
font-awesome.min.css
27 ms
js
56 ms
NAFO-LOGO-v2.png
53 ms
cv0v51gh.jpg
119 ms
fiesw4tm.jpg
54 ms
vkzr0vda.jpg
122 ms
rerbyhij.jpg
54 ms
szbkcpgw.jpg
52 ms
niw0jjz1.jpg
606 ms
igsjdkdi.jpg
122 ms
pacoejb1.jpg
120 ms
r1uwdg1j.jpg
606 ms
ittogi5d.jpg
160 ms
kahinm4j.jpg
160 ms
icq31jsk.jpg
191 ms
453d1gze.jpg
192 ms
y2cmrotq.jpg
193 ms
su0vof44.jpg
193 ms
3zlhko5r.jpg
214 ms
e4kpzqu1.jpg
693 ms
k5ktbfnw.jpg
214 ms
ksobga5m.jpg
674 ms
szu52yw2.jpg
831 ms
bw03yhh4.jpg
602 ms
mvnjb5gc.jpg
603 ms
wyjvjqbi.jpg
1149 ms
u5rm0kba.jpg
637 ms
ifmotqsv.jpg
677 ms
ICES-NAFO%20logo.jpg
877 ms
Annual%20Report-2021.jpg
778 ms
Cover-AmendedConvention.png
767 ms
CP_flags.png
717 ms
cse.js
104 ms
NAFO-banner_1.png
704 ms
raMenuTriggerIcon.png
683 ms
black-gradient.png
690 ms
loading-custom.gif
675 ms
y7lebkjgREBJK96VQi37ZtIh4imgI8P11RFo6YPCPC0.woff
63 ms
BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjojISmYWRl.woff
232 ms
BngMUXZYTXPIvIBgJJSb6ufD5qM.woff
234 ms
dazS1PrQQuCxC3iOAJFEJYUt79146ZFaIJxILcpzmhI.woff
71 ms
BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjoa4OmYWRl.woff
233 ms
BngRUXZYTXPIvIBgJJSb6u92w7CIwRs.woff
233 ms
ahcbv8612zF4jxrwMosbXsly.woff
334 ms
ahcbv8612zF4jxrwMosbXsly.woff
77 ms
AVs3lMmyGvSpQmMt6DeeRj8E0i7KZn-EPnyo3HZu7kw.woff
83 ms
ahcbv8612zF4jxrwMosbXsly.woff
335 ms
ahcev8612zF4jxrwMosT--thjGy7.woff
233 ms
ahcev8612zF4jxrwMosT6-xhjGy7.woff
234 ms
ahcev8612zF4jxrwMosT6-xhjGy7.woff
233 ms
qZpi6ZVZg3L2RL_xoBLxWRa1RVmPjeKy21_GQJaLlJI.woff
331 ms
ahcev8612zF4jxrwMosT6-xhjGy7.woff
332 ms
rss.png
649 ms
glyphicons-halflings-regular.woff
40 ms
cse_element__en.js
37 ms
default+en.css
36 ms
default.css
127 ms
light-skin-1.png
465 ms
expand-blue.png
476 ms
gradient.png
480 ms
button-nt-gradient.png
480 ms
background_image_fractallines2_dark.png
1055 ms
bottom-content-shadow.png
503 ms
facebook.png
507 ms
twitter.png
504 ms
linkedin.png
516 ms
footer-bg.png
527 ms
top-link-green.png
528 ms
top-link-arrow-green.png
532 ms
backToTopBg.png
542 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
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
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
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: