1.5 sec in total
230 ms
1.1 sec
184 ms
Welcome to 20after1.com homepage info - get ready to check 20 After 1 best content right away, or after learning these important things about 20after1.com
View sean vesce’s profile on LinkedIn, the world’s largest professional community. sean has 8 jobs listed on their profile. See the complete profile on LinkedIn and discover sean’s connections and job...
Visit 20after1.comWe analyzed 20after1.com page load time and found that the first response time was 230 ms and then it took 1.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.
20after1.com performance score
name
value
score
weighting
Value3.2 s
44/100
10%
Value3.2 s
73/100
25%
Value3.2 s
92/100
10%
Value1,190 ms
21/100
30%
Value0.028
100/100
15%
Value6.9 s
54/100
10%
230 ms
138 ms
24 ms
126 ms
6 ms
Our browser made a total of 27 requests to load all elements on the main page. We found that 78% of them (21 requests) were addressed to the original 20after1.com, 7% (2 requests) were made to Google-analytics.com and 4% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (464 ms) belongs to the original domain 20after1.com.
Page size can be reduced by 281.7 kB (49%)
576.5 kB
294.8 kB
In fact, the total size of 20after1.com main page is 576.5 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 20% of websites need less resources to load. Javascripts take 370.5 kB which makes up the majority of the site volume.
Potential reduce by 11.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. This page needs HTML code to be minified as it can gain 3.4 kB, which is 26% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 11.0 kB or 84% of the original size.
Potential reduce by 2.4 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. 20 After 1 images are well optimized though.
Potential reduce by 246.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 246.9 kB or 67% of the original size.
Potential reduce by 21.4 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. 20after1.com needs all CSS files to be minified and compressed as it can save up to 21.4 kB or 82% of the original size.
Number of requests can be reduced by 9 (36%)
25
16
The browser has sent 25 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 20 After 1. 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 from 4 to 1 for CSS and as a result speed up the page load time.
20after1.com
230 ms
default.css
138 ms
css
24 ms
galleria.classic.css
126 ms
jquery-1.4.2.min.js
6 ms
jquery.tools.min.js
7 ms
galleria-1.2.6-min.js
250 ms
galleria.video.js
120 ms
jwplayer.js
364 ms
mediaelement-and-player.min.js
167 ms
mediaelementplayer.css
106 ms
mediaelementplayer.css
153 ms
ga.js
38 ms
_na_h.png
181 ms
shine_h.png
142 ms
_tru_h.jpg
134 ms
_tra_h.jpg
174 ms
_trl_h.jpg
228 ms
_psb_h.jpg
227 ms
_dotc_h.jpg
249 ms
_mw4_h.jpg
334 ms
_sz_h.jpg
340 ms
_i76_h.jpg
362 ms
_mw2_h.jpg
440 ms
_pma_h.jpg
464 ms
-1qPjVU14dEdanR8MQuQPXYhjbSpvc47ee6xR_80Hnw.ttf
29 ms
__utm.gif
11 ms
20after1.com accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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.
20after1.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Browser errors were logged to the console
20after1.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
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 20after1.com 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 20after1.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.
20after1.com
Open Graph description is not detected on the main page of 20 After 1. 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: