Tools & Wizards About Us
nearblue.com screenshot

Report Summary

  • 28

    Performance

    Renders faster than
    48% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 93

    SEO

    Google-friendlier than
    84% of websites

nearblue.com

Near Blue African Cichlids New Jersey New York

Page Load Speed

3.7 sec in total

First Response

616 ms

Resources Loaded

2.5 sec

Page Rendered

510 ms

nearblue.com screenshot

About Website

Click here to check amazing Near Blue content. Otherwise, check out these important facts you probably never knew about nearblue.com

New Jersey and New York's premier cichlid shop, 130 tanks, 200 species, 5000 gallons

Visit nearblue.com

Key Findings

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

nearblue.com performance score

28

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.4 s

72/100

10%

LCP (Largest Contentful Paint)

Value6.4 s

10/100

25%

SI (Speed Index)

Value7.7 s

24/100

10%

TBT (Total Blocking Time)

Value5,120 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.061

97/100

15%

TTI (Time to Interactive)

Value14.4 s

9/100

10%

Network Requests Diagram

www.nearblue.com

616 ms

bt

52 ms

minified.js

64 ms

fetch.umd.js

345 ms

require.min.js

352 ms

Our browser made a total of 28 requests to load all elements on the main page. We found that 4% of them (1 request) were addressed to the original Nearblue.com, 79% (22 requests) were made to Static.parastorage.com and 14% (4 requests) were made to Frog.wix.com. The less responsive or slowest element that took the longest time to load (616 ms) belongs to the original domain Nearblue.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 744.0 kB (81%)

Content Size

920.4 kB

After Optimization

176.4 kB

  • HTML
  • JavaScript

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

HTML Optimization

-87%

Potential reduce by 738.9 kB

  • Original 852.0 kB
  • After minification 850.4 kB
  • After compression 113.1 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 738.9 kB or 87% of the original size.

JavaScript Optimization

-7%

Potential reduce by 5.0 kB

  • Original 68.4 kB
  • After minification 66.2 kB
  • After compression 63.4 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.

Requests Breakdown

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

Requests Now

23

After Optimization

4

  • Images
  • JavaScript

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

Network Requests Diagram

www.nearblue.com

www.nearblue.com

616 ms

bt

bt

52 ms

minified.js

minified.js

64 ms

fetch.umd.js

fetch.umd.js

345 ms

require.min.js

require.min.js

352 ms

874525150724b27ecb7c53aa6954e1d1.wix_mp

874525150724b27ecb7c53aa6954e1d1.wix_mp

265 ms

bg_fbshare.png

bg_fbshare.png

110 ms

facebooklogo.png

facebooklogo.png

49 ms

indented_bg_inverted.png

indented_bg_inverted.png

49 ms

indented_bg.png

indented_bg.png

51 ms

main-r.min.js

main-r.min.js

19 ms

opensans-regular-webfont.woff

opensans-regular-webfont.woff

19 ms

opensans-bold-webfont.woff

opensans-bold-webfont.woff

118 ms

b6878f57-4d64-4d70-926d-fa4dec6173a5.woff

b6878f57-4d64-4d70-926d-fa4dec6173a5.woff

117 ms

01681361-4a95-4651-a6c8-4005d0fc4a79.woff

01681361-4a95-4651-a6c8-4005d0fc4a79.woff

117 ms

bt

bt

5 ms

ugc-viewer

ugc-viewer

48 ms

lodash.min.js

lodash.min.js

65 ms

zepto.min.js

zepto.min.js

66 ms

warmupUtils.js

warmupUtils.js

64 ms

warmupUtils.min.js

warmupUtils.min.js

62 ms

layout.min.js

layout.min.js

55 ms

dataRefs.bundle.js

dataRefs.bundle.js

73 ms

imageClientApi.js

imageClientApi.js

71 ms

warmup.min.js

warmup.min.js

68 ms

santa-components-layout.prod.js

santa-components-layout.prod.js

59 ms

trg

trg

339 ms

dataRefs.bundle.min.js

dataRefs.bundle.min.js

89 ms

Accessibility Review

nearblue.com accessibility score

82

Accessibility Issues

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

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

nearblue.com SEO score

93

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

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Nearblue.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 Nearblue.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

nearblue.com

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