2.9 sec in total
436 ms
1.5 sec
879 ms
Visit forevers.in now to see the best up-to-date Forevers content for India and also check out these interesting facts you probably never knew about forevers.in
A Blog for Tech Lovers
Visit forevers.inWe analyzed Forevers.in page load time and found that the first response time was 436 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
forevers.in performance score
name
value
score
weighting
Value4.4 s
16/100
10%
Value4.9 s
29/100
25%
Value6.4 s
40/100
10%
Value340 ms
75/100
30%
Value0.01
100/100
15%
Value4.9 s
78/100
10%
436 ms
73 ms
96 ms
87 ms
84 ms
Our browser made a total of 61 requests to load all elements on the main page. We found that 98% of them (60 requests) were addressed to the original Forevers.in, 2% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (436 ms) belongs to the original domain Forevers.in.
Page size can be reduced by 342.9 kB (39%)
870.7 kB
527.9 kB
In fact, the total size of Forevers.in main page is 870.7 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. 50% of websites need less resources to load. Images take 459.4 kB which makes up the majority of the site volume.
Potential reduce by 25.4 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 25.4 kB or 80% of the original size.
Potential reduce by 39.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. Forevers images are well optimized though.
Potential reduce by 223.1 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 223.1 kB or 71% of the original size.
Potential reduce by 55.2 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. Forevers.in needs all CSS files to be minified and compressed as it can save up to 55.2 kB or 82% of the original size.
Number of requests can be reduced by 31 (55%)
56
25
The browser has sent 56 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Forevers. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
www.forevers.in
436 ms
style.css
73 ms
shortcodes.css
96 ms
flexslider.css
87 ms
colorbox.css
84 ms
fonts.css
101 ms
jquery.js
170 ms
jquery-migrate.min.js
114 ms
jpreloader.min.js
127 ms
custom.css
129 ms
media-queries.css
134 ms
css
32 ms
jquery.van.js
117 ms
wp-embed.min.js
142 ms
jquery.easing.min.js
146 ms
jquery.placeholder.js
146 ms
jquery.hoverIntent.js
152 ms
jquery.scrollTo-1.4.3.1-min.js
182 ms
jquery.localscroll-1.2.7-min.js
188 ms
jquery.nicescroll.min.js
200 ms
jquery.sticky.js
188 ms
jquery.lazyload.min.js
189 ms
jquery.flexslider-min.js
228 ms
jquery.colorbox.js
255 ms
jquery.isotope.min.js
234 ms
jquery.contact-form.js
224 ms
jquery.tweet.js
272 ms
jquery.mobilemenu.js
239 ms
jquery.superfish.js
286 ms
jquery.parallax-1.1.3.js
280 ms
jquery.simplekey.js
289 ms
general.css
237 ms
layout.css
284 ms
wp-emoji-release.min.js
138 ms
bg.jpg
228 ms
config1.png
119 ms
config3.png
121 ms
config6.png
118 ms
zahara_portfolio-320x320.png
117 ms
railway_portfolio-320x320.png
119 ms
fragzz_portfolio-320x320.png
118 ms
onclickship_portfolio-320x320.png
228 ms
onclickbazaar_portfolio-320x320.png
230 ms
royal_portfolio-320x320.png
230 ms
exprocess_portfolio-320x320.png
228 ms
order_portfolio-320x320.png
233 ms
holy_portfolio-1-320x320.png
231 ms
van_captcha.php
230 ms
UI-Elements.png
119 ms
header_img-1.png
120 ms
diamond_upholstery.png
121 ms
crissXcross.png
165 ms
debut_dark.png
202 ms
back-top.png
162 ms
overlay.png
163 ms
controls.png
163 ms
border.png
163 ms
Nexa_Free_Light-webfont.woff
161 ms
Nexa_Free_Bold-webfont.woff
196 ms
league_gothic-webfont.woff
195 ms
infinity-webfont.woff
195 ms
forevers.in 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
Image elements do not have [alt] attributes
forevers.in 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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
forevers.in SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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 Forevers.in 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 Forevers.in 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.
forevers.in
Open Graph description is not detected on the main page of Forevers. 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: