3 sec in total
567 ms
2.2 sec
235 ms
Click here to check amazing Lanex content. Otherwise, check out these important facts you probably never knew about lanex.uz
Языковые курсы в Ташкенте. Lanex предлагает курсы английского языка, IELTS, а также изучить французский, немецкий, китайский, арабский и турецкий языки
Visit lanex.uzWe analyzed Lanex.uz page load time and found that the first response time was 567 ms and then it took 2.5 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.
lanex.uz performance score
name
value
score
weighting
Value20.8 s
0/100
10%
Value31.6 s
0/100
25%
Value22.9 s
0/100
10%
Value1,520 ms
13/100
30%
Value0
100/100
15%
Value31.3 s
0/100
10%
567 ms
133 ms
274 ms
267 ms
265 ms
Our browser made a total of 50 requests to load all elements on the main page. We found that 60% of them (30 requests) were addressed to the original Lanex.uz, 20% (10 requests) were made to Static.xx.fbcdn.net and 12% (6 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (704 ms) relates to the external source Moymir.uz.
Page size can be reduced by 180.7 kB (65%)
280.0 kB
99.4 kB
In fact, the total size of Lanex.uz main page is 280.0 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 131.0 kB which makes up the majority of the site volume.
Potential reduce by 12.5 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 12.5 kB or 72% of the original size.
Potential reduce by 64.6 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, Lanex needs image optimization as it can save up to 64.6 kB or 58% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 87.2 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 87.2 kB or 67% of the original size.
Potential reduce by 16.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. Lanex.uz needs all CSS files to be minified and compressed as it can save up to 16.4 kB or 78% of the original size.
Number of requests can be reduced by 14 (29%)
48
34
The browser has sent 48 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lanex. 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 5 to 1 for CSS and as a result speed up the page load time.
lanex.uz
567 ms
default.css
133 ms
default.css
274 ms
nivo-slider.css
267 ms
jquery.fancybox.css
265 ms
jquery.min.js
409 ms
jquery.nivo.slider.js
268 ms
jquery.easing.js
274 ms
jquery.fancybox.js
395 ms
js.js
396 ms
body-top-bg.png
133 ms
f-uz.png
133 ms
f-ru.png
137 ms
i1.gif
135 ms
i2.gif
131 ms
i3.gif
135 ms
i4.gif
265 ms
i5.gif
265 ms
phone.png
265 ms
header.jpg
544 ms
menutop-bg.gif
266 ms
menutop-arw.png
271 ms
menunav-arw.gif
396 ms
top-bg1.png
395 ms
top-bg2.png
392 ms
online-cons.gif
400 ms
subs-less.gif
406 ms
skype-cons.gif
539 ms
icons.png
523 ms
footer-bg.png
522 ms
hit
259 ms
img.php
704 ms
likebox.php
188 ms
3B0ArDU4qFI.css
176 ms
WEFvPNv7jzx.css
218 ms
XCdv7aD40Gm.js
300 ms
lnwXDK64af8.js
370 ms
mn6tHWuLI-Y.js
324 ms
x8BMxYCqTb9.js
298 ms
hit
133 ms
10368382_553675184752663_8879400875477560080_n.jpg
250 ms
10300865_553669798086535_6093141413309926744_n.jpg
334 ms
11167966_10155532648440608_8905011360579024823_n.jpg
367 ms
12373316_1671738926440886_3784535816980588714_n.jpg
578 ms
1935413_1539128626410122_7646421217897560566_n.jpg
400 ms
11220075_891900397550182_7187442144006917871_n.jpg
429 ms
wL6VQj7Ab77.png
51 ms
s7jcwEQH7Sx.png
49 ms
VXcANLwwL5J.js
47 ms
50Trs1RKgUY.js
46 ms
lanex.uz 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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
lanex.uz best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
lanex.uz 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
RU
N/A
WINDOWS-1251
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lanex.uz can be misinterpreted by Google and other search engines. Our service has detected that Russian 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 Lanex.uz main page’s claimed encoding is windows-1251. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
lanex.uz
Open Graph description is not detected on the main page of Lanex. 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: