Tools & Wizards About Us
primearray.com screenshot

Report Summary

  • 90

    Performance

    Renders faster than
    91% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 74% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

primearray.com

Primearray | Enterprise NAS Servers & Data Storage Devices

Page Load Speed

1.1 sec in total

First Response

73 ms

Resources Loaded

703 ms

Page Rendered

300 ms

primearray.com screenshot

About Website

Click here to check amazing Primearray content. Otherwise, check out these important facts you probably never knew about primearray.com

PrimeArray is the leader in providing enterprise NAS Servers & Data Storage Devices. Reliable, Best storage, 24/7 Support. Get a Quote Now!

Visit primearray.com

Key Findings

We analyzed Primearray.com page load time and found that the first response time was 73 ms and then it took 1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.

Performance Metrics

primearray.com performance score

90

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.9 s

88/100

10%

LCP (Largest Contentful Paint)

Value2.6 s

87/100

25%

SI (Speed Index)

Value2.0 s

99/100

10%

TBT (Total Blocking Time)

Value150 ms

95/100

30%

CLS (Cumulative Layout Shift)

Value0.009

100/100

15%

TTI (Time to Interactive)

Value6.2 s

62/100

10%

Network Requests Diagram

primearray.com

73 ms

www.primearray.com

203 ms

logo.webp

42 ms

header-phone-icon.svg

64 ms

25-anniversy.jpg

141 ms

Our browser made a total of 77 requests to load all elements on the main page. We found that 96% of them (74 requests) were addressed to the original Primearray.com, 3% (2 requests) were made to Google-analytics.com and 1% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (205 ms) belongs to the original domain Primearray.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 170.7 kB (48%)

Content Size

353.0 kB

After Optimization

182.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Primearray.com main page is 353.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. 40% of websites need less resources to load. Javascripts take 154.6 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 56.8 kB

  • Original 72.0 kB
  • After minification 63.5 kB
  • After compression 15.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. This page needs HTML code to be minified as it can gain 8.4 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 56.8 kB or 79% of the original size.

Image Optimization

-16%

Potential reduce by 19.4 kB

  • Original 121.5 kB
  • After minification 102.1 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, Primearray needs image optimization as it can save up to 19.4 kB or 16% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-59%

Potential reduce by 90.7 kB

  • Original 154.6 kB
  • After minification 154.6 kB
  • After compression 63.9 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 90.7 kB or 59% of the original size.

CSS Optimization

-76%

Potential reduce by 3.8 kB

  • Original 5.0 kB
  • After minification 3.7 kB
  • After compression 1.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. Primearray.com needs all CSS files to be minified and compressed as it can save up to 3.8 kB or 76% of the original size.

Requests Breakdown

Number of requests can be reduced by 10 (14%)

Requests Now

72

After Optimization

62

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

primearray.com

primearray.com

73 ms

www.primearray.com

www.primearray.com

203 ms

logo.webp

logo.webp

42 ms

header-phone-icon.svg

header-phone-icon.svg

64 ms

25-anniversy.jpg

25-anniversy.jpg

141 ms

svgexport-1.svg

svgexport-1.svg

78 ms

svgexport-2.svg

svgexport-2.svg

76 ms

svgexport-3.svg

svgexport-3.svg

79 ms

svgexport-4.svg

svgexport-4.svg

80 ms

svgexport-5.svg

svgexport-5.svg

85 ms

slider.webp

slider.webp

120 ms

banner-image.webp

banner-image.webp

100 ms

box-1.webp

box-1.webp

98 ms

box-2.webp

box-2.webp

99 ms

new-new-box3.webp

new-new-box3.webp

108 ms

disk.webp

disk.webp

121 ms

primearrayhelp.webp

primearrayhelp.webp

125 ms

gray1.webp

gray1.webp

104 ms

gray2.webp

gray2.webp

111 ms

gray3.webp

gray3.webp

124 ms

gray4.webp

gray4.webp

125 ms

gray5.webp

gray5.webp

126 ms

gray6.webp

gray6.webp

134 ms

gray7.webp

gray7.webp

143 ms

gray8.webp

gray8.webp

146 ms

gray9.webp

gray9.webp

147 ms

gray10.webp

gray10.webp

147 ms

gray11.webp

gray11.webp

148 ms

gray12.webp

gray12.webp

156 ms

gray13.webp

gray13.webp

164 ms

gray14.webp

gray14.webp

168 ms

gray15.webp

gray15.webp

168 ms

gray16.webp

gray16.webp

169 ms

gray18.webp

gray18.webp

170 ms

gray19.webp

gray19.webp

178 ms

gray21.webp

gray21.webp

186 ms

gray22.webp

gray22.webp

189 ms

slick.css

slick.css

189 ms

slick-theme.css

slick-theme.css

160 ms

jquery.lazy.min.js

jquery.lazy.min.js

150 ms

jquery.min.js

jquery.min.js

185 ms

javascript.js

javascript.js

181 ms

slick.min.js

slick.min.js

191 ms

Montserrat-Medium.woff

Montserrat-Medium.woff

205 ms

background-2.webp

background-2.webp

175 ms

location.svg

location.svg

162 ms

phone-icon.svg

phone-icon.svg

170 ms

time.svg

time.svg

171 ms

facebook.svg

facebook.svg

164 ms

linkdin.svg

linkdin.svg

156 ms

pinterest.svg

pinterest.svg

155 ms

logo.webp

logo.webp

70 ms

Oswald-Medium.woff

Oswald-Medium.woff

51 ms

analytics.js

analytics.js

40 ms

gray22.webp

gray22.webp

30 ms

gray21.webp

gray21.webp

28 ms

gray19.webp

gray19.webp

29 ms

gray18.webp

gray18.webp

30 ms

gray16.webp

gray16.webp

29 ms

gray15.webp

gray15.webp

29 ms

gray1.webp

gray1.webp

48 ms

gray2.webp

gray2.webp

49 ms

gray3.webp

gray3.webp

50 ms

gray4.webp

gray4.webp

49 ms

gray5.webp

gray5.webp

50 ms

gray6.webp

gray6.webp

49 ms

gray7.webp

gray7.webp

70 ms

gray8.webp

gray8.webp

70 ms

gray9.webp

gray9.webp

71 ms

gray10.webp

gray10.webp

71 ms

gray11.webp

gray11.webp

72 ms

gray12.webp

gray12.webp

72 ms

gray13.webp

gray13.webp

92 ms

gray14.webp

gray14.webp

92 ms

slick.woff

slick.woff

92 ms

collect

collect

14 ms

js

js

70 ms

Accessibility Review

primearray.com accessibility score

90

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

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

primearray.com best practices score

67

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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

primearray.com SEO score

86

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

Crawling and Indexing

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

Impact

Issue

High

robots.txt is not valid

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

primearray.com

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