2.1 sec in total
188 ms
1.2 sec
728 ms
Click here to check amazing Fellow content for Canada. Otherwise, check out these important facts you probably never knew about fellow.co
Fellow is the best tool for meetings. From 1-on-1s to team meetings, build collaborative meeting agendas, assign action items & record decisions.
Visit fellow.coWe analyzed Fellow.co page load time and found that the first response time was 188 ms and then it took 2 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.
fellow.co performance score
name
value
score
weighting
Value2.6 s
62/100
10%
Value5.7 s
17/100
25%
Value5.4 s
57/100
10%
Value870 ms
33/100
30%
Value0.01
100/100
15%
Value11.4 s
19/100
10%
188 ms
50 ms
67 ms
66 ms
63 ms
Our browser made a total of 82 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Fellow.co, 18% (15 requests) were made to Staging.fellow.co and 7% (6 requests) were made to Fellowappdev.wpengine.com. The less responsive or slowest element that took the longest time to load (606 ms) relates to the external source Staging.fellow.co.
Page size can be reduced by 285.6 kB (27%)
1.1 MB
787.0 kB
In fact, the total size of Fellow.co main page is 1.1 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 396.1 kB which makes up the majority of the site volume.
Potential reduce by 273.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. 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 273.2 kB or 84% of the original size.
Potential reduce by 10.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. Fellow images are well optimized though.
Potential reduce by 2.2 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.
Number of requests can be reduced by 20 (26%)
76
56
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 7 to 1 for JavaScripts and as a result speed up the page load time.
fellow.app
188 ms
index.b3d2f1bd.js
50 ms
jquery-3.5.1.js
67 ms
jquery-migrate-3.3.0.js
66 ms
consent-manager-5.4.0.js
63 ms
fellow-wordmark-gray.svg
62 ms
api.js
66 ms
lazyload.min.js
38 ms
integration-logo-meet.png
44 ms
integration-logo-slack.png
48 ms
integration-logo-asana.png
47 ms
integration-logo-bamboo.png
52 ms
integration-logo-zoom.png
51 ms
integration-logo-teams.png
50 ms
Integration-logo-jira.png
56 ms
integration-logo-zapier.png
58 ms
D-Hero-Graphic-1024x957.webp
58 ms
M-Hero-Graphic.webp
61 ms
slash-peach..svg
61 ms
Lato-Regular..woff
281 ms
subset-Poppins-Regular..woff
41 ms
subset-Poppins-Medium..woff
187 ms
subset-Poppins-SemiBold..woff
179 ms
subset-Poppins-Bold..woff
41 ms
recaptcha__en.js
58 ms
Font-Awesome_-sparkles.svg
230 ms
iDeals-Headshot.png
298 ms
agenda-icon.svg
220 ms
action-items-icon.svg
223 ms
templates-icon.svg
222 ms
guidelines-icon.svg
228 ms
graph-2.svg
224 ms
Blog-Featured-Images-4.jpg
26 ms
shopify.png
17 ms
Uber.png
139 ms
universityofmichigan.png
140 ms
standforduniversity.png
140 ms
Webflow.png
141 ms
motorola.png
143 ms
Padding-for-Fanatics.png
142 ms
surveymonkey.png
142 ms
timedoctor.png
144 ms
solace-1.png
142 ms
gamesight.png
144 ms
lemonade.png
145 ms
motive.png
145 ms
vidyard-2.png
146 ms
arkoselabs.png
147 ms
D-Get-More-Done-1-1.webp
148 ms
M-Get-More-Done.webp
147 ms
D-Integrated-AI-1-1.webp
148 ms
M-Integrated-AI.webp
150 ms
D-Cross-Functional.webp
149 ms
D-Centralization.webp
148 ms
Waves.svg
151 ms
D-Carousel-AI-Meeting-scaled.webp
151 ms
D-Carousel-Agendas-scaled.webp
185 ms
D-Carousel-Action-Items-scaled.webp
184 ms
D-Carousel-Meeting-Templates-scaled.webp
185 ms
D-Carousel-Meeting-Guidelines-scaled.webp
184 ms
D-Analytics-scaled.webp
212 ms
Tobi-Headshot.png
208 ms
g2-enterprise-winter-2024.svg
206 ms
Gamesight-Headshot.png
397 ms
Lokalise-Headshot.png
448 ms
Ripple-Headshot.png
454 ms
Revv-Headshot.png
466 ms
Pliancy-Headshot.png
437 ms
Solace-Headshot.png
454 ms
Volley-Headshot.png
457 ms
Nintex-Headshot.png
547 ms
Hubspot-Headshot.png
517 ms
Spare-Headshot.png
544 ms
Frontify-Headshot-1.png
594 ms
PWL-Headshot.png
601 ms
Frontify-Headshot.png
555 ms
Poka-Headshot.png
606 ms
g2-midmarket-winter-2024.svg
202 ms
g2-momentum-winter-2024.svg
202 ms
capterra-2023.svg
193 ms
getApp.png
193 ms
software-advice.png
76 ms
fellow.co accessibility score
fellow.co 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
Page has valid source maps
fellow.co SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
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.
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: