3.7 sec in total
191 ms
2 sec
1.5 sec
Welcome to pregen.net homepage info - get ready to check Pregen best content for Russia right away, or after learning these important things about pregen.net
Premium Accounts of File Hosting and Debrid Sites
Visit pregen.netWe analyzed Pregen.net page load time and found that the first response time was 191 ms and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
pregen.net performance score
name
value
score
weighting
Value4.5 s
15/100
10%
Value5.2 s
23/100
25%
Value5.6 s
53/100
10%
Value520 ms
56/100
30%
Value0.267
46/100
15%
Value5.1 s
76/100
10%
191 ms
411 ms
235 ms
246 ms
25 ms
Our browser made a total of 61 requests to load all elements on the main page. We found that 48% of them (29 requests) were addressed to the original Pregen.net, 10% (6 requests) were made to F2.s.qip.ru and 8% (5 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source F5.s.qip.ru.
Page size can be reduced by 431.8 kB (18%)
2.4 MB
1.9 MB
In fact, the total size of Pregen.net 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. 60% of websites need less resources to load. Images take 1.9 MB which makes up the majority of the site volume.
Potential reduce by 149.1 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 149.1 kB or 90% of the original size.
Potential reduce by 53.3 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. Pregen images are well optimized though.
Potential reduce by 104.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 104.9 kB or 68% of the original size.
Potential reduce by 124.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. Pregen.net needs all CSS files to be minified and compressed as it can save up to 124.4 kB or 86% of the original size.
Number of requests can be reduced by 23 (43%)
53
30
The browser has sent 53 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pregen. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
pregen.net
191 ms
411 ms
wp-emoji-release.min.js
235 ms
animate-animo.css
246 ms
css
25 ms
style.css
242 ms
jquery.js
271 ms
jquery-migrate.min.js
183 ms
customscript.js
302 ms
css
33 ms
responsive.css
297 ms
font-awesome.min.css
339 ms
animo.min.js
380 ms
jquery.ba-throttle-debounce.min.js
381 ms
viewportchecker.js
379 ms
edsanimate.js
384 ms
edsanimate.site.js
474 ms
ssba.min.js
512 ms
wp-embed.min.js
510 ms
1049Pl6f1.png
885 ms
1049Pl6f2.png
674 ms
1049Pl6f0.png
584 ms
1049Pl6er.png
637 ms
1049Pl6eo.png
697 ms
1049Pl6e2.png
696 ms
He3ezEF.png
42 ms
1049Pl6dY.png
1195 ms
1049Pl6do.png
938 ms
1049Pl6cZ.png
570 ms
1049Pl6dN.png
569 ms
1049Pl6d0.png
662 ms
IDm6qUX.png
39 ms
7MnQ0kV.gif
40 ms
jlyoIVO.gif
39 ms
1049Pl6e9.png
663 ms
1049Pl6e5.png
800 ms
1049Pl6e3.png
932 ms
1049Pl6dn.png
568 ms
1049Pl6dm.png
680 ms
1049Pl6dO.png
1064 ms
1049Pl6dl.png
802 ms
nobg.png
169 ms
icon.png
169 ms
facebook.png
169 ms
twitter.png
169 ms
google.png
170 ms
linkedin.png
170 ms
pinterest.png
170 ms
stumbleupon.png
184 ms
tumblr.png
170 ms
diggit.png
171 ms
email.png
171 ms
1049Pl6dX.png
1107 ms
1049Pl6dP.png
676 ms
1049Pl6dj.png
566 ms
CcKI4k9un7TZVWzRVT-T8y3USBnSvpkopQaUR-2r7iU.ttf
10 ms
JbtMzqLaYbbbCL9X6EvaIy3USBnSvpkopQaUR-2r7iU.ttf
33 ms
y7lebkjgREBJK96VQi37Zp0EAVxt0G0biEntp43Qt6E.ttf
34 ms
dazS1PrQQuCxC3iOAJFEJbfB31yxOzP-czbf6AAKCVo.ttf
33 ms
10JVD_humAd5zP2yrFqw6onF5uFdDttMLvmWuJdhhgs.ttf
33 ms
fontawesome-webfont.woff
387 ms
pregen.net 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
pregen.net best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
pregen.net 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
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pregen.net can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Pregen.net 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.
pregen.net
Open Graph data is detected on the main page of Pregen. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: