2.2 sec in total
225 ms
808 ms
1.2 sec
Visit thisfellow.com now to see the best up-to-date This Fellow content for United States and also check out these interesting facts you probably never knew about thisfellow.com
Visit thisfellow.comWe analyzed Thisfellow.com page load time and found that the first response time was 225 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 40% of websites can load faster.
thisfellow.com performance score
name
value
score
weighting
Value2.7 s
61/100
10%
Value5.0 s
27/100
25%
Value5.2 s
60/100
10%
Value610 ms
49/100
30%
Value0.216
58/100
15%
Value10.8 s
22/100
10%
225 ms
42 ms
36 ms
48 ms
5 ms
Our browser made a total of 55 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Thisfellow.com, 15% (8 requests) were made to Assets.tumblr.com and 15% (8 requests) were made to Media.tumblr.com. The less responsive or slowest element that took the longest time to load (480 ms) relates to the external source Donnaylor.com.
Page size can be reduced by 519.4 kB (21%)
2.4 MB
1.9 MB
In fact, the total size of Thisfellow.com main page is 2.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. 65% of websites need less resources to load. Images take 1.7 MB which makes up the majority of the site volume.
Potential reduce by 104.0 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 104.0 kB or 80% of the original size.
Potential reduce by 55.7 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. This Fellow images are well optimized though.
Potential reduce by 359.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 359.3 kB or 63% of the original size.
Potential reduce by 384 B
CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Thisfellow.com needs all CSS files to be minified and compressed as it can save up to 384 B or 59% of the original size.
Number of requests can be reduced by 18 (34%)
53
35
The browser has sent 53 CSS, Javascripts, AJAX and image requests in order to completely render the main page of This 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 12 to 1 for JavaScripts and as a result speed up the page load time.
thisfellow.com
225 ms
pre_tumblelog.js
42 ms
tumblelog_post_message_queue.js
36 ms
stylesheet.css
48 ms
pinit.js
5 ms
index.js
81 ms
tumblr_inline_mjcwm20LVw1qc5d0n.png
155 ms
tf_bkg.jpg
324 ms
install_theme.png
154 ms
ga.js
124 ms
avatar_a3b225eeccf3_40.png
118 ms
avatar_26cae2d08274_40.png
176 ms
tumblr_inline_o3r132Z3nQ1qc5d0n_500.jpg
279 ms
tumblr_inline_o3r13pfO7Q1qc5d0n_500.jpg
118 ms
tumblr_inline_o2vkswCxqm1qc5d0n_500.jpg
151 ms
impixu
267 ms
tumblr_inline_o3r15aO1UP1qc5d0n_500.jpg
342 ms
tumblr_inline_o3r15oM8Vx1qc5d0n_500.jpg
369 ms
tumblr_inline_o2vktlgebD1qc5d0n_500.jpg
401 ms
tumblr_inline_o2vktypJR41qc5d0n_500.jpg
417 ms
tumblr_inline_o2vkuagxhL1qc5d0n_500.jpg
261 ms
tumblr_inline_o2q2mmu0Wd1qc5d0n_500.jpg
163 ms
tumblr_inline_o2q2n2H7GR1qc5d0n_500.jpg
262 ms
avatar_8e6e527ee53a_40.png
265 ms
tumblr_inline_mjcwmeqHYD1qc5d0n.png
140 ms
tumblr_inline_mjcwmwaBK01qc5d0n.png
140 ms
tumblr_inline_mjcwn1AKjD1qc5d0n.png
141 ms
tumblr_inline_mjcwm70VO01qc5d0n.png
159 ms
tumblr_inline_mjcwn6AS9V1qc5d0n.png
160 ms
tumblr_inline_mjcwmrhkVh1qc5d0n.png
131 ms
tumblr_inline_mjcwmmPeKP1qc5d0n.png
134 ms
impixu
260 ms
search.png
128 ms
icons.png
155 ms
post_bottom.png
156 ms
tf_header.png
480 ms
tf_lines.png
346 ms
tumblr_inline_o3r144yZBE1qc5d0n_500.jpg
130 ms
tumblr_inline_o2vkt6NJBZ1qc5d0n_500.jpg
125 ms
tumblr_inline_o2q2km3haF1qc5d0n_500.jpg
126 ms
tumblr_inline_o2q2lld6Le1qc5d0n_500.jpg
126 ms
pinit_main.js
278 ms
analytics.html
294 ms
login_check.html
60 ms
__utm.gif
141 ms
avatar_7b6a66596d42_40.png
44 ms
iframe_logo.png
81 ms
collect
85 ms
rapid-3.36.js
86 ms
rapidworker-1.2.js
83 ms
ga.js
66 ms
analytics.js
46 ms
cs.js
44 ms
__utm.gif
22 ms
cedexis.radar.js
5 ms
thisfellow.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
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
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.
thisfellow.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
thisfellow.com 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
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 Thisfellow.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 Thisfellow.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.
thisfellow.com
Open Graph description is not detected on the main page of This Fellow. 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: