Tools & Wizards About Us
fellow.co screenshot

Report Summary

  • 38

    Performance

    Renders faster than
    57% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 76% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

fellow.co

Fellow.app | AI Meeting Assistant and Note Taker

Page Load Speed

1.8 sec in total

First Response

33 ms

Resources Loaded

1.2 sec

Page Rendered

596 ms

fellow.co screenshot

About Website

Click here to check amazing Fellow content for Canada. Otherwise, check out these important facts you probably never knew about fellow.co

Let AI take your meeting notes. Fellow transcribes, summarizes, and gathers insights from meetings with human-level accuracy. Start for free!

Visit fellow.co

Key Findings

We analyzed Fellow.co page load time and found that the first response time was 33 ms and then it took 1.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

fellow.co performance score

38

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

61/100

10%

LCP (Largest Contentful Paint)

Value7.4 s

4/100

25%

SI (Speed Index)

Value5.0 s

63/100

10%

TBT (Total Blocking Time)

Value1,020 ms

26/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value11.6 s

18/100

10%

Network Requests Diagram

fellow.co

33 ms

fellow.app

244 ms

index.9d12b648.js

63 ms

jquery-3.5.1.js

77 ms

jquery-migrate-3.3.0.js

88 ms

Our browser made a total of 83 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Fellow.co, 87% (72 requests) were made to Fellow.app and 7% (6 requests) were made to Fellowappdev.wpengine.com. The less responsive or slowest element that took the longest time to load (544 ms) relates to the external source Staging.fellow.co.

Page Optimization Overview & Recommendations

Page size can be reduced by 264.9 kB (20%)

Content Size

1.3 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Fellow.co main page is 1.3 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. 65% of websites need less resources to load. Images take 612.8 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 260.0 kB

  • Original 310.9 kB
  • After minification 295.9 kB
  • After compression 50.9 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 260.0 kB or 84% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 612.8 kB
  • After minification 612.8 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. Fellow images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 4.9 kB

  • Original 395.5 kB
  • After minification 395.5 kB
  • After compression 390.7 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 22 (29%)

Requests Now

76

After Optimization

54

  • Images
  • JavaScript

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

Network Requests Diagram

fellow.co

fellow.co

33 ms

fellow.app

fellow.app

244 ms

index.9d12b648.js

index.9d12b648.js

63 ms

jquery-3.5.1.js

jquery-3.5.1.js

77 ms

jquery-migrate-3.3.0.js

jquery-migrate-3.3.0.js

88 ms

consent-manager-5.4.0.js

consent-manager-5.4.0.js

89 ms

5040470.js

5040470.js

52 ms

api.js

api.js

51 ms

lazyload.min.js

lazyload.min.js

40 ms

fellow-logo.png

fellow-logo.png

42 ms

integration-logo-meet.png

integration-logo-meet.png

46 ms

integration-logo-slack.png

integration-logo-slack.png

46 ms

integration-logo-asana.png

integration-logo-asana.png

80 ms

integration-logo-bamboo.png

integration-logo-bamboo.png

81 ms

integration-logo-zoom.png

integration-logo-zoom.png

83 ms

integration-logo-teams.png

integration-logo-teams.png

82 ms

Integration-logo-jira.png

Integration-logo-jira.png

81 ms

integration-logo-zapier.png

integration-logo-zapier.png

96 ms

D-Hero-Graphic-1024x957.webp

D-Hero-Graphic-1024x957.webp

90 ms

M-Hero-Graphic.webp

M-Hero-Graphic.webp

89 ms

shopify.png

shopify.png

95 ms

universityofmichigan.png

universityofmichigan.png

88 ms

standforduniversity.png

standforduniversity.png

89 ms

Webflow.png

Webflow.png

285 ms

Padding-for-Fanatics.png

Padding-for-Fanatics.png

305 ms

surveymonkey.png

surveymonkey.png

286 ms

timedoctor.png

timedoctor.png

285 ms

solace-1.png

solace-1.png

305 ms

lemonade.png

lemonade.png

305 ms

motive.png

motive.png

306 ms

vidyard-2.png

vidyard-2.png

304 ms

arkoselabs.png

arkoselabs.png

303 ms

gamesight-logo-small.webp

gamesight-logo-small.webp

324 ms

Lato-Regular.woff

Lato-Regular.woff

324 ms

recaptcha__en.js

recaptcha__en.js

49 ms

Font-Awesome_-sparkles.svg

Font-Awesome_-sparkles.svg

349 ms

Hubspot-Headshot.png

Hubspot-Headshot.png

544 ms

agenda-icon.svg

agenda-icon.svg

356 ms

action-items-icon.svg

action-items-icon.svg

355 ms

templates-icon.svg

templates-icon.svg

354 ms

guidelines-icon.svg

guidelines-icon.svg

358 ms

graph-2.svg

graph-2.svg

358 ms

Meeting-Minutes-Example.jpg

Meeting-Minutes-Example.jpg

247 ms

Uber.png

Uber.png

258 ms

motorola.png

motorola.png

270 ms

D-Integrated-AI-1-1.webp

D-Integrated-AI-1-1.webp

271 ms

M-Integrated-AI.webp

M-Integrated-AI.webp

270 ms

D-Get-More-Done-1-1.webp

D-Get-More-Done-1-1.webp

290 ms

M-Get-More-Done.webp

M-Get-More-Done.webp

273 ms

D-Cross-Functional.webp

D-Cross-Functional.webp

316 ms

D-Centralization.webp

D-Centralization.webp

289 ms

Waves.svg

Waves.svg

279 ms

D-Carousel-AI-Meeting-scaled.webp

D-Carousel-AI-Meeting-scaled.webp

298 ms

D-Carousel-Agendas-scaled.webp

D-Carousel-Agendas-scaled.webp

290 ms

D-Carousel-Action-Items-scaled.webp

D-Carousel-Action-Items-scaled.webp

296 ms

D-Carousel-Meeting-Templates-scaled.webp

D-Carousel-Meeting-Templates-scaled.webp

315 ms

D-Carousel-Meeting-Guidelines-scaled.webp

D-Carousel-Meeting-Guidelines-scaled.webp

308 ms

D-Analytics-scaled.webp

D-Analytics-scaled.webp

308 ms

iDeals-Headshot.png

iDeals-Headshot.png

310 ms

Gamesight-Headshot.png

Gamesight-Headshot.png

321 ms

Lokalise-Headshot.png

Lokalise-Headshot.png

320 ms

Ripple-Headshot.png

Ripple-Headshot.png

316 ms

Revv-Headshot.png

Revv-Headshot.png

319 ms

Pliancy-Headshot.png

Pliancy-Headshot.png

340 ms

Solace-Headshot.png

Solace-Headshot.png

316 ms

Volley-Headshot.png

Volley-Headshot.png

336 ms

subset-Poppins-Regular.woff

subset-Poppins-Regular.woff

327 ms

subset-Poppins-Medium.woff

subset-Poppins-Medium.woff

142 ms

subset-Poppins-SemiBold.woff

subset-Poppins-SemiBold.woff

142 ms

subset-Poppins-Bold.woff

subset-Poppins-Bold.woff

167 ms

Nintex-Headshot.png

Nintex-Headshot.png

153 ms

Spare-Headshot.png

Spare-Headshot.png

152 ms

Frontify-Headshot-1.png

Frontify-Headshot-1.png

152 ms

PWL-Headshot.png

PWL-Headshot.png

152 ms

Frontify-Headshot.png

Frontify-Headshot.png

153 ms

Poka-Headshot.png

Poka-Headshot.png

171 ms

Tobi-Headshot.png

Tobi-Headshot.png

154 ms

g2-enterprise-summer-2024.svg

g2-enterprise-summer-2024.svg

138 ms

g2-midmarket-summer-2024.svg

g2-midmarket-summer-2024.svg

155 ms

g2-momentum-summer-2024.svg

g2-momentum-summer-2024.svg

134 ms

capterra-2023.svg

capterra-2023.svg

134 ms

getApp.png

getApp.png

133 ms

software-advice.png

software-advice.png

136 ms

Accessibility Review

fellow.co accessibility score

91

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

[role]s do not have all required [aria-*] attributes

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.

Best Practices

fellow.co best practices score

83

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

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

fellow.co SEO score

93

Search Engine Optimization Advices

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

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 Fellow.co 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 Fellow.co 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

fellow.co

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