2.4 sec in total
483 ms
1.3 sec
625 ms
Click here to check amazing Cohere content for United States. Otherwise, check out these important facts you probably never knew about cohere.ai
Cohere provides industry-leading large language models (LLMs) and RAG capabilities tailored to meet the needs of enterprise use cases that solve real-world problems.
Visit cohere.aiWe analyzed Cohere.ai page load time and found that the first response time was 483 ms and then it took 1.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
cohere.ai performance score
name
value
score
weighting
Value2.0 s
83/100
10%
Value40.9 s
0/100
25%
Value15.7 s
0/100
10%
Value7,850 ms
0/100
30%
Value0
100/100
15%
Value53.4 s
0/100
10%
483 ms
78 ms
108 ms
147 ms
130 ms
Our browser made a total of 51 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Cohere.ai, 14% (7 requests) were made to Cdn.sanity.io. The less responsive or slowest element that took the longest time to load (598 ms) relates to the external source Cohere.com.
Page size can be reduced by 469.4 kB (11%)
4.2 MB
3.7 MB
In fact, the total size of Cohere.ai main page is 4.2 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. 60% of websites need less resources to load. Images take 4.0 MB which makes up the majority of the site volume.
Potential reduce by 136.3 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 136.3 kB or 85% of the original size.
Potential reduce by 333.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. Cohere images are well optimized though.
Number of requests can be reduced by 21 (51%)
41
20
The browser has sent 41 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Cohere. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and as a result speed up the page load time.
cohere.com
483 ms
489bebefc4d965b6.css
78 ms
f6e10f5eda297d0f.css
108 ms
polyfills-78c92fac7aa8fdd8.js
147 ms
webpack-52ea97d8cfd9b25e.js
130 ms
framework-3162bd361a5b88da.js
165 ms
main-cc75a0daad8f1dab.js
211 ms
_app-5bc6adfed1f8893c.js
200 ms
160f9a30-0ed62e95b6ffb376.js
234 ms
f69bbb46-d48282326310d960.js
203 ms
1115c941-6c1195fbdf80b4ed.js
283 ms
11ff4c8a-622a8b67e809b11c.js
243 ms
eb88b0a1-a70925cf42aeae9e.js
243 ms
967f6b59-452c0e42fd6fbe98.js
332 ms
4cc9110e-d1b869daea60671a.js
282 ms
df64f42d-ecb43b4f999c06f1.js
293 ms
2b75d063-c7c42ab354330f7e.js
293 ms
863-0e4262b5dc083b55.js
294 ms
437-fbd366f365313f64.js
439 ms
131-58100d9a455c8f85.js
296 ms
894-ffbf1db47e9d9369.js
598 ms
%5B%5B...slug%5D%5D-a43be9fab8f4313e.js
308 ms
_buildManifest.js
315 ms
_ssgManifest.js
323 ms
ae020d94b599cc453cc09ebc80be06d35d953c23-102x18.svg
124 ms
014229cb7065f56719d3cff4d3e403ee1df858e0-48x48.svg
122 ms
image
342 ms
image
349 ms
image
356 ms
image
367 ms
image
378 ms
63301010c5a3bf5238d8e04dbcbfe2ecced11db9-25x24.svg
184 ms
image
360 ms
cohere.js
363 ms
1909479147f5b8bd952f91ec21dcb707181beb48-1320x1196.png
44 ms
9429a575e4f8a36868677b820d1465ae7e145382-664x978.png
27 ms
a04177520b8f393bfc480817fef56400460ef275-1440x609.png
46 ms
253360ddd69917c0e3c76ce1e1554cb0347259d0-640x1214.png
47 ms
b2b-hero-cells-desktop.png
446 ms
b2b-hero-cells-tablet.png
413 ms
b2b-hero-cells-mobile.png
314 ms
dark-cells-bg.svg
371 ms
CohereVariable.a0eb37f8.woff
269 ms
CohereText-Regular.e692f006.woff
235 ms
CohereIcon-Default.70900a1e.woff
280 ms
https%3A%2F%2Fcdn.sanity.io%2Fimages%2Frjtqmwfu%2Fproduction%2Fa86e7b10b931351546a5296865692afac4c1ba47-1591x1784.png
226 ms
https%3A%2F%2Fcdn.sanity.io%2Fimages%2Frjtqmwfu%2Fproduction%2F1b440deff999d46506386dcf0f6b88cea1bc4b61-1591x1784.png
318 ms
https%3A%2F%2Fcdn.sanity.io%2Fimages%2Frjtqmwfu%2Fproduction%2F85a9e3d04d39494bb296938c39c64a0743199845-1520x1785.png
288 ms
https%3A%2F%2Fcdn.sanity.io%2Fimages%2Frjtqmwfu%2Fproduction%2Fd03aa3c857ac70877d9d7be7ee3da66416fcb9ae-2109x1758.png
276 ms
https%3A%2F%2Fcdn.sanity.io%2Fimages%2Frjtqmwfu%2Fproduction%2F73ac675c31ce1740e477ff2e5ac4fab96170b9b8-84x84.webp
265 ms
https%3A%2F%2Fcdn.sanity.io%2Fimages%2Frjtqmwfu%2Fproduction%2F1968122add038e469d2d24aa8071b3d4e33004f1-56x80.webp
257 ms
cohere.ai accessibility score
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
[aria-*] attributes do not match their roles
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
Buttons do not have an accessible name
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
cohere.ai best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
cohere.ai SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Document uses legible font sizes
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Cohere.ai 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 Cohere.ai 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.
cohere.ai
Open Graph data is detected on the main page of Cohere. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: