10.5 sec in total
286 ms
7.4 sec
2.8 sec
Welcome to longines.ru homepage info - get ready to check Longines best content for Russia right away, or after learning these important things about longines.ru
С 1832 года швейцарская часовая компания Longines предлагает опыт и качество, основанные на традициях, элегантности и эффективности
Visit longines.ruWe analyzed Longines.ru page load time and found that the first response time was 286 ms and then it took 10.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
longines.ru performance score
name
value
score
weighting
Value2.4 s
69/100
10%
Value8.1 s
2/100
25%
Value13.3 s
2/100
10%
Value3,990 ms
1/100
30%
Value0.003
100/100
15%
Value20.7 s
2/100
10%
286 ms
249 ms
3660 ms
151 ms
232 ms
Our browser made a total of 37 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Longines.ru, 81% (30 requests) were made to Longines.com and 8% (3 requests) were made to Connect.facebook.net. The less responsive or slowest element that took the longest time to load (3.7 sec) relates to the external source Longines.com.
Page size can be reduced by 1.6 MB (59%)
2.7 MB
1.1 MB
In fact, the total size of Longines.ru main page is 2.7 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. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 2.2 MB which makes up the majority of the site volume.
Potential reduce by 298.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 74.6 kB, which is 22% 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 298.8 kB or 89% of the original size.
Potential reduce by 1.3 MB
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 1.3 MB or 57% of the original size.
Potential reduce by 7 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. Longines.ru has all CSS files already compressed.
Number of requests can be reduced by 20 (80%)
25
5
The browser has sent 25 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Longines. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and as a result speed up the page load time.
longines.ru
286 ms
ru
249 ms
3660 ms
styles-m.min.css
151 ms
styles-l.min.css
232 ms
require.min.js
71 ms
requirejs-min-resolver.min.js
166 ms
baseUrlResolver.min.js
71 ms
requirejs-map.min.js
164 ms
bundle0.min.js
667 ms
bundle1.min.js
665 ms
bundle2.min.js
663 ms
bundle3.min.js
662 ms
bundle4.min.js
675 ms
bundle5.min.js
749 ms
bundle6.min.js
746 ms
bundle7.min.js
676 ms
static.min.js
666 ms
mixins.min.js
666 ms
requirejs-config.min.js
745 ms
lazysizes-custom.min.js
673 ms
kameleoon.js
855 ms
ZKVZT-M68SD-2HRLL-F8GLR-PZA6F
606 ms
OpenSansRegular.woff
471 ms
OpenSansLight.woff
967 ms
OpenSansSemiBold.woff
966 ms
OpenSansBold.woff
349 ms
icomoon.woff
163 ms
LonginesSerifHeadline-Regular.woff
221 ms
fbevents.js
253 ms
identity.js
50 ms
156701311665986
175 ms
config.json
474 ms
print.min.css
143 ms
ko.min.js
1525 ms
picturefill.min.js
181 ms
pageAnims.min.js
656 ms
longines.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
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.
longines.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
Missing source maps for large first-party JavaScript
longines.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
Document doesn't have a valid hreflang
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
RU
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Longines.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 Longines.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.
longines.ru
Open Graph description is not detected on the main page of Longines. 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: