Tools & Wizards About Us
nafo.int screenshot

Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

nafo.int

Home

Page Load Speed

3.1 sec in total

First Response

316 ms

Resources Loaded

2.6 sec

Page Rendered

182 ms

nafo.int screenshot

About Website

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.int

Key Findings

We 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.

Performance Metrics

nafo.int performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value28.3 s

0/100

10%

LCP (Largest Contentful Paint)

Value37.2 s

0/100

25%

SI (Speed Index)

Value28.3 s

0/100

10%

TBT (Total Blocking Time)

Value1,360 ms

16/100

30%

CLS (Cumulative Layout Shift)

Value0.1

90/100

15%

TTI (Time to Interactive)

Value37.9 s

0/100

10%

Network Requests Diagram

nafo.int

316 ms

nafo.int

373 ms

www.nafo.int

494 ms

js

88 ms

ej2.min.js

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 Optimization Overview & Recommendations

Page size can be reduced by 167.6 kB (3%)

Content Size

6.2 MB

After Optimization

6.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Nafo.int main page is 6.2 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.

HTML Optimization

-82%

Potential reduce by 61.7 kB

  • Original 74.9 kB
  • After minification 68.0 kB
  • After compression 13.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 61.7 kB or 82% of the original size.

Image Optimization

-4%

Potential reduce by 75.1 kB

  • Original 1.8 MB
  • After minification 1.7 MB

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.

JavaScript Optimization

-0%

Potential reduce by 15.9 kB

  • Original 3.9 MB
  • After minification 3.9 MB
  • After compression 3.9 MB

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.

CSS Optimization

-3%

Potential reduce by 14.9 kB

  • Original 488.7 kB
  • After minification 487.4 kB
  • After compression 473.8 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.

Requests Breakdown

Number of requests can be reduced by 44 (52%)

Requests Now

84

After Optimization

40

  • Images
  • JavaScript
  • CSS

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.

Network Requests Diagram

nafo.int

nafo.int

316 ms

nafo.int

nafo.int

373 ms

www.nafo.int

www.nafo.int

494 ms

js

js

88 ms

ej2.min.js

ej2.min.js

123 ms

lz-string.min.js

lz-string.min.js

39 ms

bootstrap4.css

bootstrap4.css

56 ms

bootstrap.min.css

bootstrap.min.css

45 ms

default.css

default.css

30 ms

bootstrap.min.css

bootstrap.min.css

66 ms

all.min.css

all.min.css

105 ms

base.css

base.css

815 ms

sdi8g6oiu3m.css

sdi8g6oiu3m.css

822 ms

skin.css

skin.css

823 ms

Vision.css

Vision.css

823 ms

blue.css

blue.css

829 ms

container.css

container.css

831 ms

container.css

container.css

832 ms

portal.css

portal.css

834 ms

multislider.css

multislider.css

869 ms

rateit.css

rateit.css

863 ms

Theme1.css

Theme1.css

869 ms

common.css

common.css

866 ms

eds_jq.js

eds_jq.js

889 ms

eds_jq.js

eds_jq.js

870 ms

jquery.js

jquery.js

915 ms

jquery-ui.min.js

jquery-ui.min.js

945 ms

js

js

818 ms

WebResource.axd

WebResource.axd

895 ms

ScriptResource.axd

ScriptResource.axd

916 ms

ScriptResource.axd

ScriptResource.axd

896 ms

dnn.modalpopup.js

dnn.modalpopup.js

914 ms

bootstrap.bundle.min.js

bootstrap.bundle.min.js

923 ms

main-scripts.js

main-scripts.js

924 ms

dnncore.js

dnncore.js

940 ms

eds_easing.1.3.js

eds_easing.1.3.js

942 ms

jquery.rateit_2.2.js

jquery.rateit_2.2.js

943 ms

multislider.2.51.2.min.js

multislider.2.51.2.min.js

953 ms

EasyDnnSolutions_1.1_2.2.js

EasyDnnSolutions_1.1_2.2.js

951 ms

edsAccordion-1.1.js

edsAccordion-1.1.js

966 ms

font-awesome.min.css

font-awesome.min.css

151 ms

font-awesome.min.css

font-awesome.min.css

105 ms

custom.css

custom.css

107 ms

gtm.js

gtm.js

69 ms

NAFO-LOGO-v2.png

NAFO-LOGO-v2.png

38 ms

mvnjb5gc.jpg

mvnjb5gc.jpg

131 ms

sxiknjhc.jpg

sxiknjhc.jpg

131 ms

1ig0lm3b.jpg

1ig0lm3b.jpg

39 ms

1nwyah2y.jpg

1nwyah2y.jpg

130 ms

j1t525wg.jpg

j1t525wg.jpg

130 ms

2ofqdkq0.jpg

2ofqdkq0.jpg

131 ms

biy3gxch.jpg

biy3gxch.jpg

131 ms

rt0e40bc.jpg

rt0e40bc.jpg

138 ms

1fissi2c.jpg

1fissi2c.jpg

138 ms

l1yj3aq1.jpg

l1yj3aq1.jpg

137 ms

ojgemzbw.jpg

ojgemzbw.jpg

137 ms

vnlft1ei.jpg

vnlft1ei.jpg

137 ms

ealncs2e.jpg

ealncs2e.jpg

138 ms

dhmbt1kq.jpg

dhmbt1kq.jpg

196 ms

Poster-EAFM-symposium-2025-web.jpg

Poster-EAFM-symposium-2025-web.jpg

196 ms

flags-web-01.svg

flags-web-01.svg

193 ms

flags-web-02.svg

flags-web-02.svg

181 ms

cse.js

cse.js

103 ms

NAFO-banner_1.png

NAFO-banner_1.png

161 ms

raMenuTriggerIcon.png

raMenuTriggerIcon.png

157 ms

black-gradient.png

black-gradient.png

207 ms

loading-custom.gif

loading-custom.gif

167 ms

y7lebkjgREBJK96VQi37ZtIh4imgI8P11RFo6YPCPC0.woff

y7lebkjgREBJK96VQi37ZtIh4imgI8P11RFo6YPCPC0.woff

101 ms

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjojISmYWRl.woff

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjojISmYWRl.woff

101 ms

BngMUXZYTXPIvIBgJJSb6ufD5qM.woff

BngMUXZYTXPIvIBgJJSb6ufD5qM.woff

177 ms

dazS1PrQQuCxC3iOAJFEJYUt79146ZFaIJxILcpzmhI.woff

dazS1PrQQuCxC3iOAJFEJYUt79146ZFaIJxILcpzmhI.woff

130 ms

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjoa4OmYWRl.woff

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjoa4OmYWRl.woff

131 ms

BngRUXZYTXPIvIBgJJSb6u92w7CIwRs.woff

BngRUXZYTXPIvIBgJJSb6u92w7CIwRs.woff

258 ms

ahcbv8612zF4jxrwMosbXsly.woff

ahcbv8612zF4jxrwMosbXsly.woff

176 ms

AVs3lMmyGvSpQmMt6DeeRj8E0i7KZn-EPnyo3HZu7kw.woff

AVs3lMmyGvSpQmMt6DeeRj8E0i7KZn-EPnyo3HZu7kw.woff

130 ms

ahcbv8612zF4jxrwMosbXsly.woff

ahcbv8612zF4jxrwMosbXsly.woff

130 ms

ahcev8612zF4jxrwMosT--thjGy7.woff

ahcev8612zF4jxrwMosT--thjGy7.woff

259 ms

ahcev8612zF4jxrwMosT6-xhjGy7.woff

ahcev8612zF4jxrwMosT6-xhjGy7.woff

131 ms

qZpi6ZVZg3L2RL_xoBLxWRa1RVmPjeKy21_GQJaLlJI.woff

qZpi6ZVZg3L2RL_xoBLxWRa1RVmPjeKy21_GQJaLlJI.woff

137 ms

ahcev8612zF4jxrwMosT6-xhjGy7.woff

ahcev8612zF4jxrwMosT6-xhjGy7.woff

137 ms

rss.png

rss.png

114 ms

light-skin-1.png

light-skin-1.png

104 ms

glyphicons-halflings-regular.woff

glyphicons-halflings-regular.woff

65 ms

time-blue.png

time-blue.png

110 ms

gradient.png

gradient.png

108 ms

cse_element__en.js

cse_element__en.js

46 ms

default+en.css

default+en.css

64 ms

default.css

default.css

66 ms

expand-blue.png

expand-blue.png

61 ms

async-ads.js

async-ads.js

56 ms

branding.png

branding.png

53 ms

background_image_fractallines2_dark.png

background_image_fractallines2_dark.png

104 ms

bottom-content-shadow.png

bottom-content-shadow.png

103 ms

facebook.png

facebook.png

103 ms

twitter.png

twitter.png

103 ms

linkedin.png

linkedin.png

103 ms

footer-bg.png

footer-bg.png

103 ms

top-link-green.png

top-link-green.png

107 ms

top-link-arrow-green.png

top-link-arrow-green.png

106 ms

backToTopBg.png

backToTopBg.png

109 ms

clear.png

clear.png

102 ms

Accessibility Review

nafo.int accessibility score

86

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

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

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

nafo.int best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

nafo.int SEO score

92

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    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.

Social Sharing Optimization

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: