Tools & Wizards About Us
kagins.com screenshot

Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 70

    Accessibility

    Visual factors better than
    that of 35% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

kagins.com

Specializing in early and rare US copper, pioneer, gold, and silver coins.

Page Load Speed

2 sec in total

First Response

330 ms

Resources Loaded

1.4 sec

Page Rendered

272 ms

kagins.com screenshot

About Website

Click here to check amazing Kagins content for United States. Otherwise, check out these important facts you probably never knew about kagins.com

Specializing in early and rare US copper, pioneer, territorial, gold, and silver coins.

Visit kagins.com

Key Findings

We analyzed Kagins.com page load time and found that the first response time was 330 ms and then it took 1.7 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

kagins.com performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

38/100

10%

LCP (Largest Contentful Paint)

Value6.6 s

8/100

25%

SI (Speed Index)

Value13.8 s

1/100

10%

TBT (Total Blocking Time)

Value1,640 ms

12/100

30%

CLS (Cumulative Layout Shift)

Value0.152

75/100

15%

TTI (Time to Interactive)

Value22.1 s

1/100

10%

Network Requests Diagram

www.kagins.com

330 ms

calendar.css

28 ms

custom.css

44 ms

styles-m.css

97 ms

amslick.min.css

46 ms

Our browser made a total of 146 requests to load all elements on the main page. We found that 93% of them (136 requests) were addressed to the original Kagins.com, 5% (7 requests) were made to Fonts.gstatic.com and 1% (1 request) were made to Maxcdn.bootstrapcdn.com. The less responsive or slowest element that took the longest time to load (330 ms) belongs to the original domain Kagins.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 269.2 kB (15%)

Content Size

1.8 MB

After Optimization

1.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Kagins.com main page is 1.8 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. 70% of websites need less resources to load. Images take 979.8 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 143.9 kB

  • Original 173.7 kB
  • After minification 153.1 kB
  • After compression 29.8 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. This page needs HTML code to be minified as it can gain 20.6 kB, which is 12% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 143.9 kB or 83% of the original size.

Image Optimization

-1%

Potential reduce by 10.3 kB

  • Original 979.8 kB
  • After minification 969.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. Kagins images are well optimized though.

JavaScript Optimization

-26%

Potential reduce by 111.5 kB

  • Original 428.1 kB
  • After minification 408.8 kB
  • After compression 316.7 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 111.5 kB or 26% of the original size.

CSS Optimization

-2%

Potential reduce by 3.5 kB

  • Original 213.7 kB
  • After minification 213.7 kB
  • After compression 210.2 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. Kagins.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 118 (87%)

Requests Now

136

After Optimization

18

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.kagins.com

www.kagins.com

330 ms

calendar.css

calendar.css

28 ms

custom.css

custom.css

44 ms

styles-m.css

styles-m.css

97 ms

amslick.min.css

amslick.min.css

46 ms

tooltipster.min.css

tooltipster.min.css

47 ms

swiper.min.css

swiper.min.css

47 ms

style.css

style.css

53 ms

home-page.css

home-page.css

58 ms

cms-pages.css

cms-pages.css

60 ms

rs6.min.css

rs6.min.css

62 ms

styles-l.css

styles-l.css

145 ms

require.js

require.js

84 ms

mixins.js

mixins.js

72 ms

requirejs-config.js

requirejs-config.js

76 ms

font-awesome.min.css

font-awesome.min.css

32 ms

svg-sprite.min.js

svg-sprite.min.js

77 ms

css

css

37 ms

gtm.js

gtm.js

169 ms

Kagins-314header.png

Kagins-314header.png

98 ms

arrow-bottom-xs.svg

arrow-bottom-xs.svg

97 ms

coins_block1t.jpg

coins_block1t.jpg

133 ms

largenotes_banner2t.jpg

largenotes_banner2t.jpg

133 ms

nationalnotes_block3t_1.jpg

nationalnotes_block3t_1.jpg

98 ms

donsbook_block4t.jpg

donsbook_block4t.jpg

132 ms

o__.16_feb._17_1776_continental_currency_fr_cc-19_pmg_65_epq_serial_143266_front.jpg

o__.16_feb._17_1776_continental_currency_fr_cc-19_pmg_65_epq_serial_143266_front.jpg

133 ms

o__100_1902_pb_san_antonio_ch_5179_pmg_20_serial_1268_front.jpg

o__100_1902_pb_san_antonio_ch_5179_pmg_20_serial_1268_front.jpg

181 ms

o__2_1890_treasury_note_fr_353_pmg_64_epq_serial_a51_front.jpg

o__2_1890_treasury_note_fr_353_pmg_64_epq_serial_a51_front.jpg

134 ms

o__50_1902_rs_st._louis_ch_170_fr_664_pmg_45_serial_a238155_front.jpg

o__50_1902_rs_st._louis_ch_170_fr_664_pmg_45_serial_a238155_front.jpg

208 ms

o__5_og_pontiac_il_ch_2141_black_charter_fr_399a_pmg_40_epq_serial_2392_front.jpg

o__5_og_pontiac_il_ch_2141_black_charter_fr_399a_pmg_40_epq_serial_2392_front.jpg

208 ms

jquery.js

jquery.js

205 ms

common.js

common.js

176 ms

dataPost.js

dataPost.js

177 ms

bootstrap.js

bootstrap.js

204 ms

app.js

app.js

205 ms

form-key-provider.js

form-key-provider.js

204 ms

mage-translation-dictionary.js

mage-translation-dictionary.js

245 ms

theme.js

theme.js

244 ms

Roboto-400.woff

Roboto-400.woff

241 ms

Roboto-700.woff

Roboto-700.woff

242 ms

amscroll.js

amscroll.js

144 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

28 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

40 ms

SlGDmQSNjdsmc35JDF1K5E55YMjF_7DPuGi-2fRkBI96.ttf

SlGDmQSNjdsmc35JDF1K5E55YMjF_7DPuGi-2fRkBI96.ttf

71 ms

SlGDmQSNjdsmc35JDF1K5E55YMjF_7DPuGi-NfNkBI96.ttf

SlGDmQSNjdsmc35JDF1K5E55YMjF_7DPuGi-NfNkBI96.ttf

96 ms

SlGDmQSNjdsmc35JDF1K5E55YMjF_7DPuGi-a_NkBI96.ttf

SlGDmQSNjdsmc35JDF1K5E55YMjF_7DPuGi-a_NkBI96.ttf

96 ms

0QI6MX1D_JOuGQbT0gvTJPa787weuxJBkqg.ttf

0QI6MX1D_JOuGQbT0gvTJPa787weuxJBkqg.ttf

97 ms

0QI6MX1D_JOuGQbT0gvTJPa787wsuxJBkqg.ttf

0QI6MX1D_JOuGQbT0gvTJPa787wsuxJBkqg.ttf

96 ms

domReady.js

domReady.js

72 ms

template.js

template.js

50 ms

confirm.js

confirm.js

48 ms

widget.js

widget.js

49 ms

jquery-mixin.js

jquery-mixin.js

44 ms

jquery-migrate.js

jquery-migrate.js

30 ms

main.js

main.js

28 ms

bootstrap.js

bootstrap.js

29 ms

types.js

types.js

25 ms

layout.js

layout.js

25 ms

text.js

text.js

24 ms

smart-keyboard-handler.js

smart-keyboard-handler.js

24 ms

mage.js

mage.js

24 ms

ie-class-fixer.js

ie-class-fixer.js

24 ms

underscore.js

underscore.js

33 ms

translate.js

translate.js

27 ms

modal.js

modal.js

28 ms

wrapper.js

wrapper.js

31 ms

knockout.js

knockout.js

32 ms

knockout-es5.js

knockout-es5.js

22 ms

version.js

version.js

21 ms

scripts.js

scripts.js

22 ms

main.js

main.js

22 ms

registry.js

registry.js

27 ms

js-translation.json

js-translation.json

36 ms

engine.js

engine.js

35 ms

bootstrap.js

bootstrap.js

35 ms

observable_array.js

observable_array.js

36 ms

bound-nodes.js

bound-nodes.js

44 ms

console-logger.js

console-logger.js

42 ms

modal-popup.html

modal-popup.html

42 ms

modal-slide.html

modal-slide.html

49 ms

modal-custom.html

modal-custom.html

49 ms

key-codes.js

key-codes.js

49 ms

core.js

core.js

50 ms

z-index.js

z-index.js

52 ms

arrays.js

arrays.js

22 ms

compare.js

compare.js

29 ms

misc.js

misc.js

28 ms

objects.js

objects.js

30 ms

strings.js

strings.js

30 ms

template.js

template.js

30 ms

knockout-repeat.js

knockout-repeat.js

30 ms

knockout-fast-foreach.js

knockout-fast-foreach.js

39 ms

renderer.js

renderer.js

35 ms

resizable.js

resizable.js

37 ms

i18n.js

i18n.js

37 ms

scope.js

scope.js

38 ms

range.js

range.js

40 ms

mage-init.js

mage-init.js

48 ms

keyboard.js

keyboard.js

53 ms

optgroup.js

optgroup.js

54 ms

after-render.js

after-render.js

54 ms

autoselect.js

autoselect.js

54 ms

datepicker.js

datepicker.js

56 ms

outer_click.js

outer_click.js

63 ms

fadeVisible.js

fadeVisible.js

63 ms

collapsible.js

collapsible.js

63 ms

staticChecked.js

staticChecked.js

65 ms

simple-checked.js

simple-checked.js

66 ms

bind-html.js

bind-html.js

68 ms

tooltip.js

tooltip.js

79 ms

events.js

events.js

76 ms

local.js

local.js

77 ms

color-picker.js

color-picker.js

76 ms

observable_source.js

observable_source.js

78 ms

logger.js

logger.js

76 ms

entry-factory.js

entry-factory.js

85 ms

console-output-handler.js

console-output-handler.js

86 ms

formatter.js

formatter.js

86 ms

message-pool.js

message-pool.js

87 ms

levels-pool.js

levels-pool.js

87 ms

logger-utils.js

logger-utils.js

90 ms

data.js

data.js

95 ms

disable-selection.js

disable-selection.js

94 ms

focusable.js

focusable.js

92 ms

form.js

form.js

93 ms

ie.js

ie.js

93 ms

keycode.js

keycode.js

93 ms

labels.js

labels.js

94 ms

jquery-patch.js

jquery-patch.js

94 ms

plugin.js

plugin.js

92 ms

safe-active-element.js

safe-active-element.js

93 ms

safe-blur.js

safe-blur.js

92 ms

scroll-parent.js

scroll-parent.js

93 ms

tabbable.js

tabbable.js

90 ms

unique-id.js

unique-id.js

89 ms

async.js

async.js

89 ms

loader.js

loader.js

93 ms

tooltip.html

tooltip.html

65 ms

spectrum.js

spectrum.js

67 ms

tinycolor.js

tinycolor.js

76 ms

class.js

class.js

73 ms

moment.js

moment.js

64 ms

entry.js

entry.js

61 ms

dom-observer.js

dom-observer.js

16 ms

bindings.js

bindings.js

16 ms

print.css

print.css

17 ms

Accessibility Review

kagins.com accessibility score

70

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

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

[role]s are not contained by their required parent element

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

kagins.com 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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

kagins.com SEO score

77

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

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 doesn't use 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 Kagins.com 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 Kagins.com 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

kagins.com

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