10.8 sec in total
1.3 sec
9.2 sec
257 ms
Welcome to fgn11.ir homepage info - get ready to check Fgn 11 best content for Iran right away, or after learning these important things about fgn11.ir
اجرای عایق کاری و آب بندی استخر, جکوزی پشت بام فلاورباکس آبنما با فایبرگلاس تضمینی
Visit fgn11.irWe analyzed Fgn11.ir page load time and found that the first response time was 1.3 sec and then it took 9.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
fgn11.ir performance score
name
value
score
weighting
Value4.5 s
15/100
10%
Value5.2 s
24/100
25%
Value12.2 s
3/100
10%
Value5,390 ms
0/100
30%
Value0.509
16/100
15%
Value16.6 s
5/100
10%
1344 ms
4041 ms
4460 ms
4160 ms
4153 ms
Our browser made a total of 48 requests to load all elements on the main page. We found that 90% of them (43 requests) were addressed to the original Fgn11.ir, 6% (3 requests) were made to Faibernemooneh.epage.ir and 2% (1 request) were made to Webgozar.ir. The less responsive or slowest element that took the longest time to load (5.8 sec) belongs to the original domain Fgn11.ir.
Page size can be reduced by 515.9 kB (33%)
1.6 MB
1.0 MB
In fact, the total size of Fgn11.ir main page is 1.6 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. 20% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 26.8 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 4.6 kB, which is 14% 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 26.8 kB or 80% of the original size.
Potential reduce by 172.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. Obviously, Fgn 11 needs image optimization as it can save up to 172.3 kB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 297.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 297.3 kB or 80% of the original size.
Potential reduce by 19.5 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. Fgn11.ir needs all CSS files to be minified and compressed as it can save up to 19.5 kB or 79% of the original size.
Number of requests can be reduced by 11 (25%)
44
33
The browser has sent 44 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fgn 11. 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 6 to 1 for CSS and as a result speed up the page load time.
fgn11.ir
1344 ms
style.css
4041 ms
jquery-1.4.1.min.js
4460 ms
jquery.jcarousel.pack.js
4160 ms
jquery-func.js
4153 ms
script.js
4250 ms
webkit.css
4364 ms
ticker-style.css
4497 ms
site.js
4571 ms
jquery.js
5845 ms
skdslider.min.js
4670 ms
skdslider.css
4783 ms
style.css
4876 ms
style.css
4680 ms
c.aspx
154 ms
2014-11-03_10.43.38_%D8%A7%DB%8C%D8%B2%D9%88%D9%84%D9%87%20%D9%85%D8%AE%D8%A7%D8%B2%D9%86%20%D8%A8%D8%A7%20%D9%81%D8%A7%DB%8C%D8%A8%D8%B1%DA%AF%D9%84%D8%A7%D8%B31%20..jpg
300 ms
bg.png
516 ms
logo.png
616 ms
menu.png
756 ms
ir.png
827 ms
en.png
827 ms
kr.png
963 ms
news.png
1035 ms
3.png
1175 ms
2.png
1244 ms
6.png
1248 ms
1.png
1393 ms
%D8%A7%D8%AA%D8%A7%D9%82%20%D8%B9%D9%82%D8%A8%20%D9%88%D8%A7%D9%86%D8%AA%20%D9%BE%D8%B1%D8%A7%DB%8C%D8%AF%20%D8%A7%D8%B3%D9%BE%D8%B1%D8%AA.jpg
2507 ms
%D8%A7%D8%AA%D8%A7%D9%82%20%D8%B9%D9%82%D8%A8%20%D9%88%D8%A7%D9%86%D8%AA%20%D9%85%D8%B2%D8%AF%D8%A7.jpg
1808 ms
%DA%A9%D8%A7%D9%BE%D9%88%D8%AA%20%DA%A9%D8%A7%D9%85%DB%8C%D9%88%D9%86%20NH.jpg
1873 ms
images.jpg
1673 ms
%D9%81%D8%A7%DB%8C%D8%A8%D8%B1%DA%AF%D9%84%D8%A7%D8%B3%20%D9%86%D9%85%D9%88%D9%86%D9%8787.jpg
2833 ms
%DA%AF%D9%84%D8%AF%D8%A7%D9%8629.jpg
2017 ms
%D9%81%D8%A7%DB%8C%D8%A8%D8%B1%DA%AF%D9%84%D8%A7%D8%B3%20%D9%86%D9%85%D9%88%D9%86%D9%8782.jpg
3140 ms
DSC00042.jpg
3483 ms
%D8%A7%D8%AA%D8%A7%D9%82%20%D8%B9%D9%82%D8%A8%20%D9%88%D8%A7%D9%86%D8%AA%20%D8%AA%D9%88%DB%8C%D9%88%D8%AA%D8%A7%20%D9%81%D8%A7%DB%8C%D8%A8%D8%B1%DA%AF%D9%84%D8%A7%D8%B3.jpg
2505 ms
%D8%A7%DB%8C%D8%B2%D9%88%D9%84%D9%87%20%D9%85%D8%AE%D8%A7%D8%B2%D9%86%20%D8%A8%D8%A7%20%D9%81%D8%A7%DB%8C%D8%A8%D8%B1%DA%AF%D9%84%D8%A7%D8%B3.jpg
2648 ms
2014-11-03_10.44.33_%D8%A7%DB%8C%D8%B2%D9%88%D9%84%D9%87%20%D9%85%D8%AE%D8%A7%D8%B2%D9%86%20%D8%A8%D8%A7%201.%D9%81%D8%A7%DB%8C%D8%A8%D8%B1%DA%AF%D9%84%D8%A7%D8%B3.jpg
273 ms
2014-10-26_11.31.34_%D8%A7%DB%8C%D8%B2%D9%88%D9%84%D9%87%20%D9%85%D8%AE%D8%A7%D8%B2%D9%86%20%D8%A7%D8%B3%DB%8C%D8%AF%20%D8%A8%D8%A7%20%D9%81%D8%A7%DB%8C%D8%A8%D8%B1%DA%AF%D9%84%D8%A7%D8%B3.jpg
292 ms
BYekan.woff
3118 ms
newsline.png
2835 ms
footerbg.png
1682 ms
xstat.aspx
222 ms
slide-bg-active.png
1796 ms
slide-bg.png
1889 ms
left.png
2031 ms
right.png
2098 ms
pause.png
2098 ms
fgn11.ir 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
Links do not have a discernible name
fgn11.ir best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
fgn11.ir SEO score
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
FA
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fgn11.ir can be misinterpreted by Google and other search engines. Our service has detected that Persian 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 Fgn11.ir 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.
fgn11.ir
Open Graph description is not detected on the main page of Fgn 11. 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: