25.4 sec in total
1.7 sec
23.1 sec
527 ms
Visit lahzenegar.com now to see the best up-to-date Lahzenegar content for Iran and also check out these interesting facts you probably never knew about lahzenegar.com
برگزاری باکیفیت رویداد آنلاین، ویدیو کنفرانس، وبینار و لایو استریم با لحظهنگار
Visit lahzenegar.comWe analyzed Lahzenegar.com page load time and found that the first response time was 1.7 sec and then it took 23.6 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
lahzenegar.com performance score
name
value
score
weighting
Value4.7 s
12/100
10%
Value10.8 s
0/100
25%
Value11.3 s
5/100
10%
Value3,900 ms
1/100
30%
Value0.095
91/100
15%
Value19.2 s
2/100
10%
1703 ms
865 ms
1095 ms
989 ms
1174 ms
Our browser made a total of 42 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Lahzenegar.com, 98% (41 requests) were made to Assets.lahzecdn.com. The less responsive or slowest element that took the longest time to load (20 sec) relates to the external source Assets.lahzecdn.com.
Page size can be reduced by 401.3 kB (13%)
3.2 MB
2.8 MB
In fact, the total size of Lahzenegar.com main page is 3.2 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. 35% of websites need less resources to load. Images take 2.5 MB which makes up the majority of the site volume.
Potential reduce by 244.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 244.4 kB or 82% of the original size.
Potential reduce by 156.1 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. Lahzenegar images are well optimized though.
Potential reduce by 808 B
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. This website has mostly compressed JavaScripts.
Potential reduce by 0 B
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.
Number of requests can be reduced by 11 (28%)
40
29
The browser has sent 40 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lahzenegar. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and as a result speed up the page load time.
lahzenegar.com
1703 ms
a5fdce10dc470577.css
865 ms
polyfills-c67a75d1b6f99dc8.js
1095 ms
webpack-030c169294cbf548.js
989 ms
framework-617d2703bc9efd35.js
1174 ms
main-94b602b685151a79.js
1713 ms
_app-8ef0b9850535bb99.js
1578 ms
1203-a0f811f5ef8447c4.js
1036 ms
4598-5f5e21adf0b31aa6.js
1432 ms
716-0d621e976ba409d7.js
1432 ms
8269-a7cdee113148539e.js
1452 ms
index-b59b9165590ebedc.js
1348 ms
_buildManifest.js
1522 ms
_ssgManifest.js
1599 ms
features_girl.eba397bd.png
13099 ms
fanap.04414e2f.png
739 ms
rightel.8157e69f.png
825 ms
sobhan.19b7f6d1.png
859 ms
bonyadzendegi.b83f5274.png
882 ms
sanofi.bc687157.png
905 ms
tamland.60857470.png
1437 ms
mammut.2813e17a.png
1018 ms
cinnagen.a2452522.png
1046 ms
dmond.f1b8b5de.png
1071 ms
digikala.036b7173.png
1100 ms
gov.c9058982.png
1197 ms
elecomp.fa25e87a.png
1222 ms
cobeldarou.0d794289.png
1257 ms
snapptrip.a1137bf9.png
1270 ms
orchid.c32340b0.png
1408 ms
sharif.c4cd0d57.png
1395 ms
mylady.a5cfbe0f.png
1437 ms
bazar.7f0055fc.png
1445 ms
mci.49697ba6.png
1565 ms
kaarmaan.4abb765d.png
1600 ms
screenshots.1425d219.png
20044 ms
startlaptop.e63de444.jpg
1953 ms
startwebinar.fcf3a9c4.jpg
2049 ms
enamad.44d8b5f9.png
1655 ms
daneshbonyan.f0d70c54.png
1676 ms
nezamsenfi.b155c3b8.png
1714 ms
samandehi.6ea9e1d9.png
1798 ms
lahzenegar.com accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
[role] values are not valid
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
lahzenegar.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
lahzenegar.com 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
Tap targets are not sized appropriately
![]()
N/A
![]()
FA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lahzenegar.com 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 Persian. Our system also found out that Lahzenegar.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.
lahzenegar.com
Open Graph data is detected on the main page of Lahzenegar. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: