5.7 sec in total
543 ms
4.5 sec
660 ms
Click here to check amazing GLOBUS 1 content for Russia. Otherwise, check out these important facts you probably never knew about globus1.ru
Продажа туров из Москвы и Санкт-Петербурга по доступным ценам в туристической компании «GLOBUS».
Visit globus1.ruWe analyzed Globus1.ru page load time and found that the first response time was 543 ms and then it took 5.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
globus1.ru performance score
name
value
score
weighting
Value5.0 s
10/100
10%
Value6.4 s
9/100
25%
Value11.3 s
5/100
10%
Value6,120 ms
0/100
30%
Value0.836
4/100
15%
Value17.9 s
4/100
10%
543 ms
706 ms
384 ms
382 ms
697 ms
Our browser made a total of 91 requests to load all elements on the main page. We found that 58% of them (53 requests) were addressed to the original Globus1.ru, 16% (15 requests) were made to Clients.streamwood.ru and 9% (8 requests) were made to Module.sletat.ru. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Clients.streamwood.ru.
Page size can be reduced by 592.2 kB (36%)
1.6 MB
1.0 MB
In fact, the total size of Globus1.ru 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. 45% of websites need less resources to load. Images take 650.3 kB which makes up the majority of the site volume.
Potential reduce by 35.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. This page needs HTML code to be minified as it can gain 10.3 kB, which is 23% 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 35.4 kB or 79% of the original size.
Potential reduce by 20.0 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. GLOBUS 1 images are well optimized though.
Potential reduce by 216.7 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 216.7 kB or 51% of the original size.
Potential reduce by 320.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. Globus1.ru needs all CSS files to be minified and compressed as it can save up to 320.0 kB or 63% of the original size.
Number of requests can be reduced by 38 (44%)
86
48
The browser has sent 86 CSS, Javascripts, AJAX and image requests in order to completely render the main page of GLOBUS 1. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
globus1.ru
543 ms
www.globus1.ru
706 ms
style.css
384 ms
jquery.fancybox-1.3.2.css
382 ms
sw.css
697 ms
sw.js
1071 ms
jquery.js
1013 ms
css_browser_selector.js
267 ms
jquery_redy.js
402 ms
jquery.fancybox-1.3.2.pack.js
534 ms
jquery.easing-1.3.pack.js
528 ms
linker.js
319 ms
core.js
1049 ms
ga.js
74 ms
bg.jpg
203 ms
logo.png
281 ms
tl_309.jpg
185 ms
bg_cp.png
185 ms
vodopad.png
399 ms
header_href_active.png
186 ms
header_href.png
272 ms
text.png
378 ms
menu.png
276 ms
border-left.png
294 ms
star.png
373 ms
Egypet.jpg
633 ms
bl_261.jpg
397 ms
bl_210.jpg
398 ms
bl_352.jpg
626 ms
bl_154.jpg
630 ms
bl_246.jpg
630 ms
bl_329.jpg
632 ms
bl_107.jpg
631 ms
bl_337.jpg
641 ms
bl_372.jpg
633 ms
bd_307.jpg
640 ms
bd_40.jpg
651 ms
bd_338.jpg
660 ms
bd_59.jpg
661 ms
bd_42.jpg
746 ms
bd_330.jpg
752 ms
bd_389.jpg
763 ms
bd_380.jpg
780 ms
bd_293.jpg
786 ms
vkontakte-32.png
786 ms
list_image.png
891 ms
tr_121.jpg
867 ms
theme-standard-1.css
652 ms
load.gif
732 ms
country_about_link.png
762 ms
country_a_hover.png
762 ms
country_a.png
761 ms
spech.png
879 ms
pred_a.png
872 ms
__utm.gif
32 ms
bg_spech.png
790 ms
right_menu.png
828 ms
right_header.png
828 ms
bg_footer.png
813 ms
hit
342 ms
footer_logo.png
861 ms
168 ms
close.png
147 ms
148 ms
sound.png
135 ms
manager-bg.png
167 ms
good.png
279 ms
bad.png
308 ms
upload_file.png
414 ms
logo-default.png
414 ms
generator-picture.png
747 ms
counter-bgr.png
414 ms
recall-close.png
416 ms
hit
135 ms
PTSansRegular.woff
1333 ms
css
59 ms
css
60 ms
watch.js
232 ms
GetSettingsV2
398 ms
GetDepartCities
371 ms
GetDepartCities
369 ms
watch.js
467 ms
GetCountries
261 ms
GetCountries
262 ms
advert.gif
101 ms
GetCities
149 ms
GetTourDates
376 ms
1
112 ms
1
101 ms
1
99 ms
GetHotelStars
132 ms
globus1.ru 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 input fields do not have accessible names
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
globus1.ru 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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
globus1.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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Globus1.ru can be misinterpreted by Google and other search engines. Our service has detected that Russian is used on the page, and it does not match the claimed English language. Our system also found out that Globus1.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.
globus1.ru
Open Graph description is not detected on the main page of GLOBUS 1. 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: