Tools & Wizards About Us
buildarray.com screenshot

Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

buildarray.com

Online Form Builder, Data Collection Using Mobile and Desktop

Page Load Speed

10.3 sec in total

First Response

219 ms

Resources Loaded

6 sec

Page Rendered

4.1 sec

buildarray.com screenshot

About Website

Visit buildarray.com now to see the best up-to-date Buildarray content for United States and also check out these interesting facts you probably never knew about buildarray.com

Array – Easy to Use Online Form Builder. Collect data using mobile IOS & Android and desktop devices. Free to try, 1000s of templates.

Visit buildarray.com

Key Findings

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

Performance Metrics

buildarray.com performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

21/100

10%

LCP (Largest Contentful Paint)

Value13.4 s

0/100

25%

SI (Speed Index)

Value13.4 s

2/100

10%

TBT (Total Blocking Time)

Value3,570 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.013

100/100

15%

TTI (Time to Interactive)

Value28.8 s

0/100

10%

Network Requests Diagram

buildarray.com

219 ms

buildarray.com

286 ms

www.buildarray.com

895 ms

content-fonts.9e14ad2560edeb77e004.css

137 ms

array-setup.js

599 ms

Our browser made a total of 68 requests to load all elements on the main page. We found that 68% of them (46 requests) were addressed to the original Buildarray.com, 7% (5 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.1 sec) relates to the external source Salesiq.zohopublic.eu.

Page Optimization Overview & Recommendations

Page size can be reduced by 233.2 kB (25%)

Content Size

918.5 kB

After Optimization

685.3 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Buildarray.com main page is 918.5 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 585.0 kB which makes up the majority of the site volume.

HTML Optimization

-70%

Potential reduce by 191.4 kB

  • Original 274.5 kB
  • After minification 243.6 kB
  • After compression 83.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. This page needs HTML code to be minified as it can gain 31.0 kB, which is 11% 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 191.4 kB or 70% of the original size.

Image Optimization

-6%

Potential reduce by 35.6 kB

  • Original 585.0 kB
  • After minification 549.4 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. Buildarray images are well optimized though.

JavaScript Optimization

-10%

Potential reduce by 6.2 kB

  • Original 59.0 kB
  • After minification 59.0 kB
  • After compression 52.8 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 38 (66%)

Requests Now

58

After Optimization

20

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

buildarray.com

buildarray.com

219 ms

buildarray.com

buildarray.com

286 ms

www.buildarray.com

www.buildarray.com

895 ms

content-fonts.9e14ad2560edeb77e004.css

content-fonts.9e14ad2560edeb77e004.css

137 ms

array-setup.js

array-setup.js

599 ms

content.50d61b3c197f31310aee.css

content.50d61b3c197f31310aee.css

238 ms

jquery-515520a004.js

jquery-515520a004.js

240 ms

site-header-ff4ab49694.js

site-header-ff4ab49694.js

220 ms

owl-carousel-c7323d133e.js

owl-carousel-c7323d133e.js

366 ms

content.home.5ca7bea9ca9601516164.css

content.home.5ca7bea9ca9601516164.css

366 ms

owl-carousel.afb9ec1739dd9c02dad4.css

owl-carousel.afb9ec1739dd9c02dad4.css

365 ms

logos-banner.3e890c1ddb4b2269b88c.css

logos-banner.3e890c1ddb4b2269b88c.css

365 ms

content-rotator-91077292e1.js

content-rotator-91077292e1.js

365 ms

case-study-carousel-4a24329b95.js

case-study-carousel-4a24329b95.js

474 ms

slideshow-carousel-691f3fb8d9.js

slideshow-carousel-691f3fb8d9.js

475 ms

counter-boxes-fe8952194f.js

counter-boxes-fe8952194f.js

474 ms

case-study-snippet-carousel-97b7b2489a.js

case-study-snippet-carousel-97b7b2489a.js

474 ms

related-articles-carousel-346121e73b.js

related-articles-carousel-346121e73b.js

474 ms

pill-carousel-f2c09a3b4f.js

pill-carousel-f2c09a3b4f.js

981 ms

on-scroll-change-color-b23b89c96c.js

on-scroll-change-color-b23b89c96c.js

975 ms

jquery-ui-d8f518d74a.js

jquery-ui-d8f518d74a.js

1201 ms

sixteen.global-9335999799.js

sixteen.global-9335999799.js

913 ms

base-8b424be36f.js

base-8b424be36f.js

1200 ms

gradient-horizontal-background.9796f0f774097a82e590.bundle.js

gradient-horizontal-background.9796f0f774097a82e590.bundle.js

1479 ms

5671336.js

5671336.js

124 ms

css

css

101 ms

css

css

116 ms

gtm.js

gtm.js

221 ms

fbevents.js

fbevents.js

331 ms

340 ms

lftracker_v1_YEgkB8lqyEJ7ep3Z.js

lftracker_v1_YEgkB8lqyEJ7ep3Z.js

1285 ms

741 ms

scan-app.png

scan-app.png

734 ms

animated-hero-spacer.png

animated-hero-spacer.png

735 ms

array-icon-flat-logo.svg

array-icon-flat-logo.svg

712 ms

tasks.svg

tasks.svg

735 ms

automation%20icon.svg

automation%20icon.svg

711 ms

doc%20workflow%20icon.svg

doc%20workflow%20icon.svg

721 ms

reporting%20icon.svg

reporting%20icon.svg

761 ms

forms-icon-dark.svg

forms-icon-dark.svg

778 ms

apps-wall.png

apps-wall.png

798 ms

array-flows.svg

array-flows.svg

723 ms

array-workflow-editor.png

array-workflow-editor.png

794 ms

formview-icon.svg

formview-icon.svg

721 ms

tools-button.png

tools-button.png

798 ms

forms-icon-bw.svg

forms-icon-bw.svg

799 ms

docs-icon-bw.svg

docs-icon-bw.svg

799 ms

flow-icon-bw.svg

flow-icon-bw.svg

814 ms

reports-icon-bw.svg

reports-icon-bw.svg

804 ms

home%20inspection.jpg

home%20inspection.jpg

815 ms

office-birds-eye-view-cropped.jpg

office-birds-eye-view-cropped.jpg

815 ms

electrical%20inspection.jpg

electrical%20inspection.jpg

819 ms

fire%20alarm%20inspection.jpg

fire%20alarm%20inspection.jpg

816 ms

fire%20door%20inspection.jpg

fire%20door%20inspection.jpg

818 ms

365 ms

pxiByp8kv8JHgFVrLGT9Z1xlEw.woff

pxiByp8kv8JHgFVrLGT9Z1xlEw.woff

1233 ms

pxiEyp8kv8JHgFVrJJfedA.woff

pxiEyp8kv8JHgFVrJJfedA.woff

1226 ms

pxiByp8kv8JHgFVrLEj6Z1xlEw.woff

pxiByp8kv8JHgFVrLEj6Z1xlEw.woff

1224 ms

pxiByp8kv8JHgFVrLCz7Z1xlEw.woff

pxiByp8kv8JHgFVrLCz7Z1xlEw.woff

1225 ms

pxiByp8kv8JHgFVrLDD4Z1xlEw.woff

pxiByp8kv8JHgFVrLDD4Z1xlEw.woff

1225 ms

Material-Design-Iconic-Font.woff

Material-Design-Iconic-Font.woff

1631 ms

tr-rc.lfeeder.com

tr-rc.lfeeder.com

1807 ms

widget

widget

2147 ms

5671336.js

5671336.js

1747 ms

fb.js

fb.js

1781 ms

5671336.js

5671336.js

1800 ms

w.js

w.js

1777 ms

settings.luckyorange.net

settings.luckyorange.net

65 ms

Accessibility Review

buildarray.com accessibility score

73

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 have valid values

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

Links do not have a discernible name

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

buildarray.com best practices score

75

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

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

buildarray.com SEO score

84

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

Links are not crawlable

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Buildarray.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Buildarray.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

buildarray.com

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