Tools & Wizards About Us
nekofigs.com screenshot

Report Summary

  • 55

    Performance

    Renders faster than
    72% of other websites

  • 92

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

nekofigs.com

The NekoFigs Blog - Anime Figure Collecting Blog, Unboxing and Reviews

Page Load Speed

3.7 sec in total

First Response

248 ms

Resources Loaded

1.2 sec

Page Rendered

2.2 sec

nekofigs.com screenshot

About Website

Welcome to nekofigs.com homepage info - get ready to check Neko Figs best content right away, or after learning these important things about nekofigs.com

Anime figure news, anime figure collecting guide, anime figure unboxing and reviews for the avid collector.

Visit nekofigs.com

Key Findings

We analyzed Nekofigs.com page load time and found that the first response time was 248 ms and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

nekofigs.com performance score

55

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.6 s

64/100

10%

LCP (Largest Contentful Paint)

Value4.1 s

47/100

25%

SI (Speed Index)

Value3.2 s

92/100

10%

TBT (Total Blocking Time)

Value890 ms

32/100

30%

CLS (Cumulative Layout Shift)

Value0.064

97/100

15%

TTI (Time to Interactive)

Value8.5 s

38/100

10%

Network Requests Diagram

nekofigs.com

248 ms

gppstub.js

169 ms

js

121 ms

frontend-gtag.min.js

26 ms

jquery.min.js

122 ms

Our browser made a total of 62 requests to load all elements on the main page. We found that 58% of them (36 requests) were addressed to the original Nekofigs.com, 27% (17 requests) were made to Ezojs.com and 8% (5 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (480 ms) relates to the external source Ezojs.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 187.5 kB (35%)

Content Size

534.0 kB

After Optimization

346.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Nekofigs.com main page is 534.0 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. 50% of websites need less resources to load. HTML takes 228.0 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 184.4 kB

  • Original 228.0 kB
  • After minification 228.0 kB
  • After compression 43.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 184.4 kB or 81% of the original size.

Image Optimization

-1%

Potential reduce by 1.4 kB

  • Original 109.0 kB
  • After minification 107.6 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. Neko Figs images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 1.6 kB

  • Original 145.9 kB
  • After minification 145.8 kB
  • After compression 144.3 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.

CSS Optimization

-0%

Potential reduce by 196 B

  • Original 51.1 kB
  • After minification 51.1 kB
  • After compression 50.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. Nekofigs.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 48 (86%)

Requests Now

56

After Optimization

8

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

nekofigs.com

nekofigs.com

248 ms

gppstub.js

gppstub.js

169 ms

js

js

121 ms

frontend-gtag.min.js

frontend-gtag.min.js

26 ms

jquery.min.js

jquery.min.js

122 ms

tpbr_front.min.js

tpbr_front.min.js

49 ms

ccpaplus.js

ccpaplus.js

221 ms

dismiss.js

dismiss.js

38 ms

hoverIntent.min.js

hoverIntent.min.js

45 ms

superfish.min.js

superfish.min.js

79 ms

superfish.args.min.js

superfish.args.min.js

121 ms

skip-links.min.js

skip-links.min.js

50 ms

move-entry-dates.js

move-entry-dates.js

149 ms

responsive-menus.min.js

responsive-menus.min.js

75 ms

e-202410.js

e-202410.js

123 ms

OneSignalSDK.js

OneSignalSDK.js

351 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

269 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

217 ms

wp-polyfill.min.js

wp-polyfill.min.js

348 ms

dom-ready.min.js

dom-ready.min.js

352 ms

hooks.min.js

hooks.min.js

344 ms

i18n.min.js

i18n.min.js

361 ms

a11y.min.js

a11y.min.js

361 ms

newsletter-block-functions.js

newsletter-block-functions.js

377 ms

boise.js

boise.js

246 ms

abilene.js

abilene.js

292 ms

tulsa.js

tulsa.js

288 ms

et.js

et.js

291 ms

lazy_load.js

lazy_load.js

480 ms

cropped-logo-760x180-1.png

cropped-logo-760x180-1.png

97 ms

nekofigs-blog-banner.jpg

nekofigs-blog-banner.jpg

119 ms

rem-wedding-version-pha-featured-1.jpg

rem-wedding-version-pha-featured-1.jpg

97 ms

cd-japan-aff-1.png

cd-japan-aff-1.png

124 ms

Baltimore-Finish-Line-Flagbearer-Ver-APEX-featured.webp

Baltimore-Finish-Line-Flagbearer-Ver-APEX-featured.webp

114 ms

symbol-defs.svg

symbol-defs.svg

111 ms

css_onload.js

css_onload.js

113 ms

drake.js

drake.js

117 ms

jellyfish.js

jellyfish.js

128 ms

screx.js

screx.js

77 ms

mulvane.js

mulvane.js

37 ms

wichita.js

wichita.js

80 ms

raleigh.js

raleigh.js

80 ms

vista.js

vista.js

81 ms

style-blocks.build.css

style-blocks.build.css

53 ms

style.css

style.css

53 ms

style.min.css

style.min.css

50 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

56 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

19 ms

dashicons.min.css

dashicons.min.css

55 ms

css

css

57 ms

front-end.css

front-end.css

168 ms

style.css

style.css

246 ms

jetpack.css

jetpack.css

170 ms

olathe.js

olathe.js

155 ms

vitals.js

vitals.js

159 ms

chanute.js

chanute.js

159 ms

script_delay.js

script_delay.js

61 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrQ.ttf

20 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCIPrQ.ttf

39 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtzpbCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtzpbCIPrQ.ttf

73 ms

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

103 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

104 ms

Accessibility Review

nekofigs.com accessibility score

92

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.

Best Practices

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

Missing source maps for large first-party JavaScript

SEO Factors

nekofigs.com SEO score

100

Search Engine Optimization Advices

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

nekofigs.com

Open Graph data is detected on the main page of Neko Figs. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: