9.4 sec in total
542 ms
7.7 sec
1.1 sec
Welcome to free-lines.ru homepage info - get ready to check Free Lines best content for Russia right away, or after learning these important things about free-lines.ru
Free Lines Company — надежная транспортная компания для международных грузоперевозок в Россию. Доставка коммерческих грузов, быстрая и безопасная перевозка
Visit free-lines.ruWe analyzed Free-lines.ru page load time and found that the first response time was 542 ms and then it took 8.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
free-lines.ru performance score
name
value
score
weighting
Value10.4 s
0/100
10%
Value27.0 s
0/100
25%
Value27.6 s
0/100
10%
Value9,640 ms
0/100
30%
Value0.004
100/100
15%
Value42.5 s
0/100
10%
542 ms
1829 ms
1001 ms
69 ms
956 ms
Our browser made a total of 130 requests to load all elements on the main page. We found that 58% of them (76 requests) were addressed to the original Free-lines.ru, 5% (7 requests) were made to Unpkg.com and 4% (5 requests) were made to Mc.yandex.com. The less responsive or slowest element that took the longest time to load (4.2 sec) belongs to the original domain Free-lines.ru.
Page size can be reduced by 1.3 MB (26%)
5.2 MB
3.8 MB
In fact, the total size of Free-lines.ru main page is 5.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. 65% of websites need less resources to load. Images take 3.8 MB which makes up the majority of the site volume.
Potential reduce by 459.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. This page needs HTML code to be minified as it can gain 174.6 kB, which is 34% 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 459.5 kB or 89% of the original size.
Potential reduce by 601.8 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, Free Lines needs image optimization as it can save up to 601.8 kB or 16% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 43.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. This website has mostly compressed JavaScripts.
Potential reduce by 212.0 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. Free-lines.ru needs all CSS files to be minified and compressed as it can save up to 212.0 kB or 76% of the original size.
Number of requests can be reduced by 73 (65%)
112
39
The browser has sent 112 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Free Lines. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 43 to 1 for JavaScripts and from 22 to 1 for CSS and as a result speed up the page load time.
free-lines.ru
542 ms
free-lines.ru
1829 ms
tag.js
1001 ms
gtm.js
69 ms
container_JRp6WjX9.js
956 ms
jquery.min.js
42 ms
js.cookie.min.js
59 ms
fancybox.css
157 ms
fancybox.umd.js
390 ms
swiper-bundle.min.css
419 ms
swiper-bundle.min.js
666 ms
swiper-bundle.min.js
50 ms
custom.js
550 ms
team.js
546 ms
about.js
546 ms
sidebar.js
547 ms
core@2
59 ms
tippy.js@6
85 ms
country.js
543 ms
service.js
671 ms
customers.js
672 ms
build.css
805 ms
styles.css
675 ms
template_styles.css
678 ms
popup-banner.css
792 ms
custom.css
796 ms
team.css
800 ms
about.css
815 ms
vacancy.css
817 ms
history.css
920 ms
contacts.css
921 ms
charity.css
925 ms
news.css
930 ms
sidebar.css
931 ms
country.css
938 ms
tooltip.css
1067 ms
service.css
1066 ms
config.css
1069 ms
customers.css
1068 ms
core.js
1450 ms
core_fx.js
1076 ms
build.js
1439 ms
basket.js
1197 ms
main.js
1196 ms
analytics.js
1198 ms
css2
43 ms
leaflet.css
79 ms
leaflet.js
173 ms
1058 ms
lmvRxmcCKD
652 ms
logo.png
1192 ms
core@2.11.8
27 ms
popper.min.js
22 ms
analytics.js
55 ms
fbevents.js
23 ms
code.js
873 ms
tippy-bundle.umd.min.js
35 ms
wheel.png
2573 ms
collect
14 ms
collect
28 ms
js
58 ms
ga-audiences
213 ms
employees.svg
933 ms
clients.svg
911 ms
declaration.svg
790 ms
orders.svg
917 ms
1.jpg
920 ms
2.jpg
920 ms
3.jpg
1942 ms
cyrpuj1geckrclrpfb8qjpmn03d51hsh.jpeg
1952 ms
lgulozg4zyrjmcnojw300e4cltmlildt.jpg
1946 ms
openapi.a2ed73393cad04481c1dfb3f7794921f.js
245 ms
uu2k1mg7sl0c2doo283bwfg6f17lwemf.png
1944 ms
99mpi304w281fbj3patg62z7i4qmhinz.png
1814 ms
3cnhaayi160511xq71fhlmqtlg22obtm.jpg
1939 ms
7sjofq98l950wylvagtywm938rmb3pxm.png
1825 ms
ahhnj6qnq071uy69osdjaxi6mkfmq1n5.jpeg
1925 ms
n7yei4ng134yll0ubr67g4zwd8jdcv24.png
1926 ms
d8mzt0mswza47soj6atb5aysaddfmtzw.jpg
1911 ms
cbm25bplgv5axipqptmhupyzvro253hb.JPG
1912 ms
w4wd8weteil9rkmjma5g7u69k7yi8jjm.png
1915 ms
rtrg
149 ms
6i2f73097abigsmne80cimxn3snpzqy6.png
1938 ms
f191s9h1vebqzr33qildfhl3hri45bxi.jpeg
1936 ms
wwb8ittrpn0xlxdk4xau68sv76zeikw4.jpeg
1935 ms
lst7svk42zbhd41nqg0ns1vms22qjc4o.jpeg
1930 ms
bj8i3z4vlfiipqr3vjceo5wekscxgs2o.jpeg
2073 ms
aq4g00k1ns0fbayl9o8hjqezhadttivo.png
2463 ms
sync-loader.js
1747 ms
counter
139 ms
3fiasby2ff7oupy2yyd9mytud89y4cdp.jpg
2175 ms
banner.jpg
4240 ms
akrobat-regular.woff
1915 ms
akrobat-semibold.woff
1929 ms
akrobat-bold.woff
2070 ms
akrobat-black.woff
1932 ms
ba.js
1220 ms
KFOmCnqEu92Fr1Me5mZNCzc.woff
52 ms
KFOlCnqEu92Fr1MmEU9vAB0_IsE.woff
103 ms
KFOlCnqEu92Fr1MmSU5vAB0_IsE.woff
120 ms
KFOlCnqEu92Fr1MmWUlvAB0_IsE.woff
120 ms
init.js
918 ms
lk-w.svg
680 ms
sprite.svg
774 ms
calcw.svg
782 ms
select-arrow.svg
795 ms
urban-sprite.png
174 ms
bg-goods.png
994 ms
bg-map.png
893 ms
full-e375679eab0e00a5e81ddbb027f673d8841bde2c.js
1828 ms
gray-image.png
1182 ms
init
1293 ms
lmvRxmcCKD
405 ms
dyn-goal-config.js
140 ms
advert.gif
160 ms
bx_stat
184 ms
sync_cookie_image_decide
362 ms
api.js
24 ms
1
144 ms
lmvRxmcCKD
593 ms
sync_cookie_image_decide_secondary
147 ms
addVisit
449 ms
feedback.js
752 ms
grab.cur
148 ms
grabbing.cur
166 ms
help.cur
314 ms
zoom_in.cur
422 ms
1
286 ms
counter.js
354 ms
popup.js
119 ms
free-lines.ru accessibility score
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
Buttons do not have an accessible name
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
free-lines.ru 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
Page has valid source maps
free-lines.ru SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
Tap targets are not sized appropriately
![]()
RU
![]()
RU
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Free-lines.ru can be misinterpreted by Google and other search engines. Our service has detected that Russian is used on the page, and it matches the claimed language. Our system also found out that Free-lines.ru 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.
free-lines.ru
Open Graph description is not detected on the main page of Free Lines. 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: