7.8 sec in total
1.5 sec
5.9 sec
297 ms
Visit 4thgen.org now to see the best up-to-date 4th Gen content and also check out these interesting facts you probably never knew about 4thgen.org
Visit 4thgen.orgWe analyzed 4thgen.org page load time and found that the first response time was 1.5 sec and then it took 6.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
4thgen.org performance score
name
value
score
weighting
Value4.4 s
17/100
10%
Value7.0 s
6/100
25%
Value6.2 s
43/100
10%
Value340 ms
74/100
30%
Value0.002
100/100
15%
Value7.7 s
46/100
10%
1530 ms
72 ms
1192 ms
198 ms
157 ms
Our browser made a total of 74 requests to load all elements on the main page. We found that 74% of them (55 requests) were addressed to the original 4thgen.org, 5% (4 requests) were made to Google-analytics.com and 4% (3 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain 4thgen.org.
Page size can be reduced by 655.0 kB (51%)
1.3 MB
636.0 kB
In fact, the total size of 4thgen.org 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. 60% of websites need less resources to load. CSS take 510.7 kB which makes up the majority of the site volume.
Potential reduce by 36.7 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 36.7 kB or 80% of the original size.
Potential reduce by 49.5 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. 4th Gen images are well optimized though.
Potential reduce by 137.9 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 137.9 kB or 60% of the original size.
Potential reduce by 430.9 kB
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. 4thgen.org needs all CSS files to be minified and compressed as it can save up to 430.9 kB or 84% of the original size.
Number of requests can be reduced by 39 (53%)
73
34
The browser has sent 73 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 4th Gen. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.
www.4thgen.org
1530 ms
style.css
72 ms
www.4thgen.org
1192 ms
tfg_style.css
198 ms
styles.css
157 ms
styles.css
162 ms
style.css
162 ms
style.css
152 ms
comments.css
239 ms
css
25 ms
custom-style.css
253 ms
wp-paginate.css
229 ms
css3_gray_glossy.css
389 ms
jquery.js
568 ms
jquery-migrate.min.js
423 ms
external-tracking.min.js
307 ms
css
34 ms
site.js
751 ms
jquery.min.js
26 ms
script.js
762 ms
basic-jquery-slider.js
764 ms
widgets.js
5 ms
plusone.js
33 ms
in.js
7 ms
jquery.form.min.js
507 ms
scripts.js
581 ms
social.js
638 ms
wp-embed.min.js
662 ms
moment.js
725 ms
langs.min.js
817 ms
jquery.touchSwipe.min.js
806 ms
jquery.easing.1.3.js
820 ms
ditty-news-ticker.js
831 ms
style.css
833 ms
ga.js
21 ms
wp-emoji-release.min.js
82 ms
__utm.gif
15 ms
__utm.gif
61 ms
city-ad.jpg
497 ms
partner-ad.jpg
497 ms
top-banner.jpg
772 ms
nav-back.jpg
484 ms
content-background.jpg
540 ms
sign-up.jpg
484 ms
panel.jpg
715 ms
slideshow-image-02.gif
664 ms
slideshow-image-01.gif
903 ms
slideshow-image-03.jpg
895 ms
img-but-01.jpg
780 ms
img-but-02.jpg
781 ms
img-but-03.jpg
788 ms
vision.jpg
849 ms
blog-bar-place.png
865 ms
calendar-bar-place.png
867 ms
on-air-ad.jpg
1135 ms
ministry-ad.jpg
1219 ms
belongs-ad.jpg
1142 ms
book-nav.jpg
944 ms
nyack.jpg
994 ms
meet-jack.jpg
967 ms
facebook-link.png
1005 ms
twitter-link.png
1040 ms
blog-link.png
1052 ms
search.png
1075 ms
cb=gapi.loaded_0
202 ms
secureAnonymousFramework
215 ms
__utm.gif
159 ms
baAIDqLDMpo
79 ms
MW2DGDoI-d4
80 ms
LDpDEt0chzw
92 ms
www-embed-player-vflfNyN_r.css
37 ms
www-embed-player.js
78 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
56 ms
ad_status.js
53 ms
4thgen.org accessibility score
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
Image elements do not have [alt] attributes
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
4thgen.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
4thgen.org 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
Image elements do not have [alt] attributes
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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 4thgen.org 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 4thgen.org 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.
4thgen.org
Open Graph description is not detected on the main page of 4th Gen. 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: