Your Website Score is

Similar Ranking

31
国联资源网_中国领先的B2B电子商务集群,高效的链商资源整合服务网络
ibicn.com
31
REVOLVE (リボルブ)で、有名デザイナーズブランドの洋服をショッピング
revolveclothing.co.jp
31
VOITURE AU MAROC - VOITURE OCCASION AU MAROC - ANNONCES MOTEUR.MA
moteur.ma
31
مكتبة نور - تحميل كتب PDF
noor-book.com
31
BEST WIFI BROADBAND & INTERNET SERVICE PROVIDER (ISP) IN INDIA | TIKONA INFINET PRIVATE LIMITED
tikona.in
31
DOWNLOAD--- SOFTWARE FOR WINDOWS - JALECO.COM
jaleco.com
31
نماشا - سرویس رایگان اشتراک ویدیو
namasha.com

Latest Sites

14
PORTSTONE PARTNERS LIMITED
portstonepartnersltd.com
14
VENICTRADE.COM
venictrade.com
14
COINLUNO.COM
coinluno.com
14
SIGNCURRENCY.COM
signcurrency.com
14
ALLTRADESFX.COM
alltradesfx.com
19
MODERN KITCHENS | READIKIT | HOME PAGE
readikit.com
1

Top Technologies

Nginx
Web Servers
Google Tag Manager
Tag Managers
Google Font API
Font Scripts
CloudFlare
CDN
Apache
Web Servers
Font Awesome
Font Scripts
WordPress
CMS
Twitter Bootstrap
Web Frameworks

31 msu.ru Last Updated: 10 months

Success 70% of passed verification steps
Warning 15% of total warning
Errors 15% of total errors, require fast action

Desktop

Mobile

Performance Desktop Score 40%
Best Practices Desktop Score 77%
SEO Desktop Score 90%
Progressive Web App Desktop Score 27%
Performance Mobile Score 6%
Best Practices Mobile Score 77%
SEO Mobile Score 88%
Progressive Web App Mobile Score 26%
Page Authority Authority 0%
Domain Authority Domain Authority 0%
Moz Rank 0.0/10
Bounce Rate Rate 0%
Charset Encoding
Great, language/character encoding is specified: UTF-8
Title Tag 59 Characters
МОСКОВСКИЙ ГОСУДАРСТВЕННЫЙ УНИВЕРСИТЕТ ИМЕНИ М.В.ЛОМОНОСОВА
Meta Description 85 Characters
Официальный сайт Московского государственного университета имени М.В.Ломоносова (МГУ)
Effective URL 18 Characters
https://www.msu.ru
Excerpt Page content
Московский государственный университет имени М.В.Ломоносова Московский государственный университет имени М.В.Ломоносова Основан в 1755 году ...
Keywords Cloud Density
универсиада24 ломоносов20 имени18 благодарность17 университета15 апреля14 декабря14 ломоносова13 московского13 февраля12
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
универсиада 24
ломоносов 20
имени 18
благодарность 17
университета 15
апреля 14
декабря 14
ломоносова 13
московского 13
февраля 12
Google Preview Your look like this in google search result
МОСКОВСКИЙ ГОСУДАРСТВЕННЫЙ УНИВЕРСИТЕТ ИМЕНИ М.В.ЛОМОНОСОВА
https://www.msu.ru
Официальный сайт Московского государственного университета имени М.В.Ломоносова (МГУ)
Robots.txt File Detected
Sitemap.xml File Detected
Whois Is a query and response protocol that is widely used for querying databases that store the registered users or assignees of an Internet resource, such as a domain name, an IP address block, or an autonomous system
Updated: 1970-01-01 / 51 years
Create on: 1996-12-01 / 24 years
Expires on: 2019-12-31 / 9 months 24 days

RU-CENTER-RU ,

Nameservers
ns1.orc.ru.
ns3.nic.fr.
ns.msu.net.
ns.msu.ru.
93.180.0.1
Page Size Code & Text Ratio
Document Size: ~93.87 KB
Code Size: ~42.21 KB
Text Size: ~51.66 KB Ratio: 55.03%

Estimation Traffic and Earnings

Only Registered Users

Sign up for see all features and reviews about this site

Login

Technologies

PWA - Manifest

Manifest is not valid
Your site don't have valid manifest.json, read more in Web App Manifest

Desktop

Desktop Screenshot
Total Blocking Time 50 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
JavaScript execution time 0.7 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Server Backend Latencies 0 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance
Properly size images Potential savings of 96 KB
Serve images that are appropriately-sized to save cellular data and improve load time
Speed Index 3.3 s
Speed Index shows how quickly the contents of a page are visibly populated
First CPU Idle 3.4 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. [Learn more](https://web.dev/first-cpu-idle).
Avoids enormous network payloads Total size was 1,762 KB
Large network payloads cost users real money and are highly correlated with long load times
Minimizes main-thread work 1.1 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
First Contentful Paint 3.3 s
First Contentful Paint marks the time at which the first text or image is painted
Includes front-end JavaScript libraries with known security vulnerabilities 4 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Avoid chaining critical requests 53 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load
Avoids an excessive DOM size 176 elements
A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow)
Preload key requests Potential savings of 130 ms
Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load
Minify JavaScript Potential savings of 102 KB
Minifying JavaScript files can reduce payload sizes and script parse time
First Meaningful Paint 3.4 s
First Meaningful Paint measures when the primary content of a page is visible
Keep request counts low and transfer sizes small 104 requests • 1,765 KB
To set budgets for the quantity and size of page resources, add a budget.json file
Serve static assets with an efficient cache policy 86 resources found
A long cache lifetime can speed up repeat visits to your page
Max Potential First Input Delay 60 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task
Time to Interactive 3.5 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Network Round Trip Times 0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance
Page load is not fast enough on mobile networks Interactive on simulated mobile network at 15.2 s
A fast page load over a cellular network ensures a good mobile user experience
Estimated Input Latency 10 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy
Minify CSS Potential savings of 3 KB
Minifying CSS files can reduce network payload sizes
Remove unused CSS Potential savings of 11 KB
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity
Serve images in next-gen formats Potential savings of 29 KB
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
Reduce server response times (TTFB) Root document took 3,030 ms
Time To First Byte identifies the time at which your server sends a response
Eliminate render-blocking resources Potential savings of 1,810 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Minimize third-party usage Third-party code blocked the main thread for 50 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading

Mobile

Mobile Screenshot
First CPU Idle 11.4 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. [Learn more](https://web.dev/first-cpu-idle).
Avoids enormous network payloads Total size was 1,588 KB
Large network payloads cost users real money and are highly correlated with long load times
Minimize main-thread work 4.1 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
First Contentful Paint 11.4 s
First Contentful Paint marks the time at which the first text or image is painted
Includes front-end JavaScript libraries with known security vulnerabilities 4 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Avoid chaining critical requests 52 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load
Avoids an excessive DOM size 176 elements
A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow)
Preload key requests Potential savings of 180 ms
Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load
Minify JavaScript Potential savings of 102 KB
Minifying JavaScript files can reduce payload sizes and script parse time
First Meaningful Paint 11.4 s
First Meaningful Paint measures when the primary content of a page is visible
Keep request counts low and transfer sizes small 95 requests • 1,590 KB
To set budgets for the quantity and size of page resources, add a budget.json file
Serve static assets with an efficient cache policy 80 resources found
A long cache lifetime can speed up repeat visits to your page
Max Potential First Input Delay 220 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task
Time to Interactive 14.5 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Network Round Trip Times 0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance
Page load is not fast enough on mobile networks Interactive at 14.5 s
A fast page load over a cellular network ensures a good mobile user experience
First Contentful Paint (3G) 23190 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
Estimated Input Latency 60 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy
Minify CSS Potential savings of 3 KB
Minifying CSS files can reduce network payload sizes
Tap targets are not sized appropriately 64% appropriately sized tap targets
Interactive elements like buttons and links should be large enough (48x48px), and have enough space around them, to be easy enough to tap without overlapping onto other elements
Document uses legible font sizes 96.65% legible text
Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px
Remove unused CSS Potential savings of 12 KB
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity
Serve images in next-gen formats Potential savings of 29 KB
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
Server response times are low (TTFB) Root document took 290 ms
Time To First Byte identifies the time at which your server sends a response
Eliminate render-blocking resources Potential savings of 5,700 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Reduce the impact of third-party code Third-party code blocked the main thread for 570 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading
Total Blocking Time 350 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Reduce JavaScript execution time 2.6 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Defer offscreen images Potential savings of 4 KB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Server Backend Latencies 0 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance
Speed Index 11.4 s
Speed Index shows how quickly the contents of a page are visibly populated

Speed And Optimization Tips

Only Registered Users

Sign up for see all features and reviews about this site

Login

Alexa Rank

0

Local Rank: / Users: / PageViews:

Global Rank

Information Server

Response Header HTTP headers carry information about the client browser, the requested page and the server
HTTP/1.1 200 OK
Server: nginx/1.4.7
Date: Tue, 17 Dec 2019 01:30:09 GMT
Content-Type: text/html; charset=UTF-8
Connection: keep-alive
X-Powered-By: PHP/7.1.12
P3P: policyref="/bitrix/p3p.xml", CP="NON DSP COR CUR ADM DEV PSA PSD OUR UNR BUS UNI COM NAV INT DEM STA"
X-Powered-CMS: Bitrix Site Manager (552a5ddd7314b6f656bb860f094678c1)
Set-Cookie: PHPSESSID=e28e9195682b84a6ff4c4805829301e4; path=/; HttpOnly
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate
Pragma: no-cache
X-Frame-Options: SAMEORIGIN
Set-Cookie: SK_LANG_RD=1; expires=Thu, 16-Jan-2020 01:30:09 GMT; Max-Age=2592000; path=/
Set-Cookie: MSU_GUEST_ID=30114978; expires=Fri, 11-Dec-2020 01:30:09 GMT; Max-Age=31104000; path=/
Set-Cookie: MSU_LAST_VISIT=17.12.2019+04%3A30%3A09; expires=Fri, 11-Dec-2020 01:30:09 GMT; Max-Age=31104000; path=/
Content-Encoding: gzip
Access-Control-Allow-Origin: *
X-Content-Type-Options: nosniff
DNS Records DNS Resource Records associated with a hostname
View DNS Records

Comments

Add extension to Chrome