Tools & Wizards About Us
go.algolia.com screenshot

Report Summary

  • 32

    Performance

    Renders faster than
    52% of other websites

  • 72

    Accessibility

    Visual factors better than
    that of 37% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

go.algolia.com

Hosted Site Search & Discovery for Companies of All Sizes | Algolia

Page Load Speed

22.6 sec in total

First Response

138 ms

Resources Loaded

21.1 sec

Page Rendered

1.4 sec

go.algolia.com screenshot

About Website

Click here to check amazing Go Algolia content for United States. Otherwise, check out these important facts you probably never knew about go.algolia.com

Algolia helps businesses across industries quickly create relevant, scalable, and lightning fast Search and Discovery experiences.

Visit go.algolia.com

Key Findings

We analyzed Go.algolia.com page load time and found that the first response time was 138 ms and then it took 22.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

go.algolia.com performance score

32

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

54/100

10%

LCP (Largest Contentful Paint)

Value3.2 s

71/100

25%

SI (Speed Index)

Value12.0 s

4/100

10%

TBT (Total Blocking Time)

Value6,090 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.229

54/100

15%

TTI (Time to Interactive)

Value32.4 s

0/100

10%

Network Requests Diagram

go.algolia.com

138 ms

go.algolia.com

165 ms

www.algolia.com

222 ms

db7952f434c74498.css

75 ms

a18c75704cc7327e.css

52 ms

Our browser made a total of 105 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Go.algolia.com, 62% (65 requests) were made to Res.cloudinary.com and 32% (34 requests) were made to Algolia.com. The less responsive or slowest element that took the longest time to load (20.2 sec) relates to the external source Algolia.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 365.0 kB (26%)

Content Size

1.4 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Go.algolia.com main page is 1.4 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. 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 996.4 kB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 352.6 kB

  • Original 405.7 kB
  • After minification 405.5 kB
  • After compression 53.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 352.6 kB or 87% of the original size.

Image Optimization

-1%

Potential reduce by 12.2 kB

  • Original 996.4 kB
  • After minification 984.2 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. Go Algolia images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 115 B

  • Original 21.4 kB
  • After minification 21.4 kB
  • After compression 21.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.

Requests Breakdown

Number of requests can be reduced by 46 (46%)

Requests Now

101

After Optimization

55

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

go.algolia.com

go.algolia.com

138 ms

go.algolia.com

go.algolia.com

165 ms

www.algolia.com

www.algolia.com

222 ms

db7952f434c74498.css

db7952f434c74498.css

75 ms

a18c75704cc7327e.css

a18c75704cc7327e.css

52 ms

polyfills-c67a75d1b6f99dc8.js

polyfills-c67a75d1b6f99dc8.js

355 ms

webpack-b19058e8b4c9355f.js

webpack-b19058e8b4c9355f.js

56 ms

framework-3dd0632da82b5311.js

framework-3dd0632da82b5311.js

55 ms

main-8ccbe05a61c5e3a7.js

main-8ccbe05a61c5e3a7.js

43 ms

_app-dfc87835f7f5b7b6.js

_app-dfc87835f7f5b7b6.js

394 ms

5731161a-b3bf8817a55409bd.js

5731161a-b3bf8817a55409bd.js

392 ms

9338-5d9e56bd9e92d4d7.js

9338-5d9e56bd9e92d4d7.js

393 ms

7463-68dbbc91362f3d49.js

7463-68dbbc91362f3d49.js

393 ms

4285-72e3c43b6b82e479.js

4285-72e3c43b6b82e479.js

394 ms

384-8d3829c7435fcdfb.js

384-8d3829c7435fcdfb.js

407 ms

4763-9bb1cf68be38e6ec.js

4763-9bb1cf68be38e6ec.js

407 ms

6684-d20be8b051b52998.js

6684-d20be8b051b52998.js

408 ms

5994-67c188f0f6313e41.js

5994-67c188f0f6313e41.js

424 ms

1277-9d8ef5cdac2e394b.js

1277-9d8ef5cdac2e394b.js

427 ms

8275-7f25d361fbaa1b16.js

8275-7f25d361fbaa1b16.js

427 ms

6961-73ec9a9da6ac8e6d.js

6961-73ec9a9da6ac8e6d.js

430 ms

6450-17533974818761a5.js

6450-17533974818761a5.js

430 ms

7850-d5837d3c699adae8.js

7850-d5837d3c699adae8.js

429 ms

7032-8b4cc1dbe21ca357.js

7032-8b4cc1dbe21ca357.js

455 ms

2855-ae56bdaa3161d444.js

2855-ae56bdaa3161d444.js

476 ms

index-38d2b7f227630a67.js

index-38d2b7f227630a67.js

452 ms

_buildManifest.js

_buildManifest.js

452 ms

_ssgManifest.js

_ssgManifest.js

455 ms

core.js+ssdomvar.js+generic-adapter.js

core.js+ssdomvar.js+generic-adapter.js

445 ms

ai-blue.svg

ai-blue.svg

367 ms

281 ms

345 ms

341 ms

264 ms

434 ms

398 ms

20248 ms

browse-blue.svg

browse-blue.svg

121 ms

recommendations-blue.svg

recommendations-blue.svg

152 ms

merch-blue.svg

merch-blue.svg

124 ms

pie-blue.svg

pie-blue.svg

144 ms

ui-components-blue.svg

ui-components-blue.svg

154 ms

adobe.svg

adobe.svg

128 ms

bigcommerce-icon_1.svg

bigcommerce-icon_1.svg

133 ms

commercetools-symbol.svg

commercetools-symbol.svg

148 ms

salesforce.svg

salesforce.svg

158 ms

shopify.svg

shopify.svg

156 ms

retail-blue.svg

retail-blue.svg

164 ms

b2b-blue.svg

b2b-blue.svg

159 ms

marketplaces-blue.svg

marketplaces-blue.svg

163 ms

media-blue.svg

media-blue.svg

197 ms

saas-blue.svg

saas-blue.svg

170 ms

desktop-blue.svg

desktop-blue.svg

176 ms

documentation-blue.svg

documentation-blue.svg

195 ms

integrations-blue.svg

integrations-blue.svg

323 ms

autocomplete-blue.svg

autocomplete-blue.svg

177 ms

codex-blue.svg

codex-blue.svg

181 ms

eng-blog-blue.svg

eng-blog-blue.svg

184 ms

community-blue.svg

community-blue.svg

188 ms

events-blue.svg

events-blue.svg

193 ms

quickstart-blue.svg

quickstart-blue.svg

195 ms

opensource-blue.svg

opensource-blue.svg

197 ms

api-blue.svg

api-blue.svg

239 ms

support-blue.svg

support-blue.svg

212 ms

blog-blue.svg

blog-blue.svg

202 ms

resource-blue.svg

resource-blue.svg

247 ms

customer-stories-blue.svg

customer-stories-blue.svg

205 ms

onboarding-blue.svg

onboarding-blue.svg

209 ms

academy-blue.svg

academy-blue.svg

212 ms

newsroom-blue.svg

newsroom-blue.svg

216 ms

profit-sim-blue.svg

profit-sim-blue.svg

241 ms

grader-blue.svg

grader-blue.svg

220 ms

OtAutoBlock.js

OtAutoBlock.js

80 ms

otSDKStub.js

otSDKStub.js

93 ms

search-audit-blue.svg

search-audit-blue.svg

178 ms

company-blue.svg

company-blue.svg

126 ms

partners-blue.svg

partners-blue.svg

171 ms

globe-white.svg

globe-white.svg

123 ms

alltrails.svg

alltrails.svg

122 ms

culture-king.svg

culture-king.svg

131 ms

decathlon.png

decathlon.png

421 ms

gymshark.svg

gymshark.svg

126 ms

manomano.png

manomano.png

188 ms

medium.svg

medium.svg

183 ms

slack.svg

slack.svg

261 ms

5e9f5149-bde8-4a13-b973-b7a9385e8ebb.json

5e9f5149-bde8-4a13-b973-b7a9385e8ebb.json

30 ms

swedol.png

swedol.png

306 ms

the-times.svg

the-times.svg

210 ms

ltk.png

ltk.png

208 ms

swedol.png

swedol.png

189 ms

hershey.png

hershey.png

204 ms

shoe-carnival.svg

shoe-carnival.svg

228 ms

brex.svg

brex.svg

361 ms

notion.png

notion.png

439 ms

y-combinator.png

y-combinator.png

417 ms

location

location

31 ms

retool.svg

retool.svg

475 ms

asana.svg

asana.svg

333 ms

javascript.svg

javascript.svg

508 ms

react.svg

react.svg

460 ms

android.svg

android.svg

383 ms

vue.svg

vue.svg

407 ms

angular.svg

angular.svg

447 ms

ios.svg

ios.svg

440 ms

Features_Do_it_visually_35.svg

Features_Do_it_visually_35.svg

516 ms

Accessibility Review

go.algolia.com accessibility score

72

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

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

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

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

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

go.algolia.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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

go.algolia.com SEO score

92

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

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

    EN

  • Encoding

    UTF-8

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

go.algolia.com

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