Tools & Wizards About Us
navypedia.org screenshot

Report Summary

  • 43

    Performance

    Renders faster than
    62% of other websites

  • 67

    Accessibility

    Visual factors better than
    that of 32% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

navypedia.org

NAVYPEDIA - fighting ships of the world

Page Load Speed

2.5 sec in total

First Response

692 ms

Resources Loaded

1.4 sec

Page Rendered

409 ms

navypedia.org screenshot

About Website

Click here to check amazing NAVYPEDIA content for South Korea. Otherwise, check out these important facts you probably never knew about navypedia.org

Navypedia - historical reference site dedicated to all the world fighting ships and navies of XIX - XXI centuries including both World wars. Site contains information about fates of ships, their tech...

Visit navypedia.org

Key Findings

We analyzed Navypedia.org page load time and found that the first response time was 692 ms and then it took 1.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

navypedia.org performance score

43

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

39/100

10%

LCP (Largest Contentful Paint)

Value3.6 s

61/100

25%

SI (Speed Index)

Value6.9 s

33/100

10%

TBT (Total Blocking Time)

Value1,860 ms

9/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value9.6 s

29/100

10%

Network Requests Diagram

navypedia.org

692 ms

plusone.js

111 ms

branding.css

229 ms

-11011.css

232 ms

show_ads.js

8 ms

Our browser made a total of 39 requests to load all elements on the main page. We found that 8% of them (3 requests) were addressed to the original Navypedia.org, 23% (9 requests) were made to Google.com and 18% (7 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (692 ms) belongs to the original domain Navypedia.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 30.6 kB (49%)

Content Size

62.4 kB

After Optimization

31.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Navypedia.org main page is 62.4 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. 45% of websites need less resources to load. HTML takes 29.6 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 24.3 kB

  • Original 29.6 kB
  • After minification 28.7 kB
  • After compression 5.3 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 24.3 kB or 82% of the original size.

Image Optimization

-11%

Potential reduce by 671 B

  • Original 6.2 kB
  • After minification 5.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, NAVYPEDIA needs image optimization as it can save up to 671 B or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-19%

Potential reduce by 4.7 kB

  • Original 25.3 kB
  • After minification 25.3 kB
  • After compression 20.5 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 4.7 kB or 19% of the original size.

CSS Optimization

-65%

Potential reduce by 896 B

  • Original 1.4 kB
  • After minification 1.2 kB
  • After compression 490 B

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. Navypedia.org needs all CSS files to be minified and compressed as it can save up to 896 B or 65% of the original size.

Requests Breakdown

Number of requests can be reduced by 19 (54%)

Requests Now

35

After Optimization

16

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 35 CSS, Javascripts, AJAX and image requests in order to completely render the main page of NAVYPEDIA. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

navypedia.org

navypedia.org

692 ms

plusone.js

plusone.js

111 ms

branding.css

branding.css

229 ms

-11011.css

-11011.css

232 ms

show_ads.js

show_ads.js

8 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

21 ms

ga.js

ga.js

29 ms

adp88_31.gif

adp88_31.gif

36 ms

review-dark-125x60.png

review-dark-125x60.png

14 ms

counter.php

counter.php

34 ms

__utm.gif

__utm.gif

24 ms

ca-pub-2806390211315959.js

ca-pub-2806390211315959.js

63 ms

zrt_lookup.html

zrt_lookup.html

62 ms

show_ads_impl.js

show_ads_impl.js

63 ms

iframe.html

iframe.html

55 ms

branding.css

branding.css

28 ms

poweredby_FFFFFF.gif

poweredby_FFFFFF.gif

76 ms

newsshow+af.css

newsshow+af.css

72 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

59 ms

fastbutton

fastbutton

91 ms

branding.css

branding.css

81 ms

ads

ads

131 ms

osd.js

osd.js

60 ms

postmessageRelay

postmessageRelay

93 ms

jsapi

jsapi

48 ms

ads

ads

136 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

64 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

65 ms

W5F8_SL0XFawnjxHGsZjJA.ttf

W5F8_SL0XFawnjxHGsZjJA.ttf

149 ms

ads

ads

165 ms

newsshow+en.css

newsshow+en.css

12 ms

default,slideshow,newsshow+en.I.js

default,slideshow,newsshow+en.I.js

12 ms

news

news

507 ms

cleardot.gif

cleardot.gif

16 ms

element-noborder-726x88.gif

element-noborder-726x88.gif

16 ms

api.js

api.js

46 ms

core:rpc:shindig.random:shindig.sha1.js

core:rpc:shindig.random:shindig.sha1.js

76 ms

2536007149-postmessagerelay.js

2536007149-postmessagerelay.js

70 ms

abg.js

abg.js

34 ms

Accessibility Review

navypedia.org accessibility score

67

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

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.

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

navypedia.org best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

navypedia.org SEO score

85

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

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    WINDOWS-1252

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Navypedia.org 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 Navypedia.org main page’s claimed encoding is windows-1252. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

navypedia.org

Open Graph description is not detected on the main page of NAVYPEDIA. 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: