85 semrush.com Last Updated: 3 years

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

Desktop Speed Score

Mobile Speed Score

Performance Desktop Score 90%
Best Practices Desktop Score 87%
SEO Desktop Score 92%
Progressive Web App Desktop Score 64%
Performance Mobile Score 41%
Best Practices Mobile Score 87%
SEO Mobile Score 100%
Progressive Web App Mobile Score 67%
Page Authority Authority 64%
Domain Authority Domain Authority 87%
Moz Rank 6.4/10
Bounce Rate Rate 0%
Charset Encoding
Great, language/character encoding is specified: UTF-8
Title Tag 47 Characters
SEMRUSH - ONLINE VISIBILITY MANAGEMENT PLATFORM
Meta Description 130 Characters
Semrush offers solutions for SEO, PPC, content, social media and competitive research. Trusted by over 7000000 marketers worldwide
Effective URL 19 Characters
https://semrush.com
Excerpt Page content
Semrush - Online Visibility Management Platform ...
Keywords Cloud Density
semrush34 marketing24 content22 social13 media12 tools11 tool9 market8 founder7 advertising7
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
semrush 34
marketing 24
content 22
social 13
media 12
tools 11
tool 9
market 8
founder 7
advertising 7
Google Preview Your look like this in google search result
SEMRUSH - ONLINE VISIBILITY MANAGEMENT PLATFORM
https://semrush.com
Semrush offers solutions for SEO, PPC, content, social media and competitive research. Trusted by over 7000000 marketers worldwide
Robots.txt File Detected
Sitemap.xml File Detected
Page Size Code & Text Ratio
Document Size: ~194.24 KB
Code Size: ~126.65 KB
Text Size: ~67.59 KB Ratio: 34.80%

semrush.com Estimation Traffic and Earnings

76,987
Unique Visits
Daily
142,425
Pages Views
Daily
$138
Income
Daily
2,155,636
Unique Visits
Monthly
4,059,113
Pages Views
Monthly
$3,450
Income
Monthly
24,943,788
Unique Visits
Yearly
47,854,800
Pages Views
Yearly
$36,432
Income
Yearly

Desktop Speed Score

Desktop Screenshot
Avoid serving legacy JavaScript to modern browsers Potential savings of 0 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers
User Timing marks and measures 3 user timings
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences
Serve static assets with an efficient cache policy 7 resources found
A long cache lifetime can speed up repeat visits to your page
JavaScript execution time 0.3 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Keep request counts low and transfer sizes small 97 requests • 582 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Total Blocking Time 30 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Remove unused JavaScript Potential savings of 34 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Enable text compression Potential savings of 7 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
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
Some third-party resources can be lazy loaded with a facade 1 facade alternative available
Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required
Avoid long main-thread tasks 3 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
First Contentful Paint 1.0 s
First Contentful Paint marks the time at which the first text or image is painted
Defer offscreen images Potential savings of 60 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Largest Contentful Paint 1.0 s
Largest Contentful Paint marks the time at which the largest text or image is painted
First Meaningful Paint 1.0 s
First Meaningful Paint measures when the primary content of a page is visible
Avoid an excessive DOM size 1,160 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)
Avoids enormous network payloads Total size was 582 KiB
Large network payloads cost users real money and are highly correlated with long load times
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
Cumulative Layout Shift 0.004
Cumulative Layout Shift measures the movement of visible elements within the viewport
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
Max Potential First Input Delay 60 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Minimize third-party usage Third-party code blocked the main thread for 60 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
Avoid large layout shifts 5 elements found
These DOM elements contribute most to the CLS of the page.
Speed Index 1.9 s
Speed Index shows how quickly the contents of a page are visibly populated
Avoid multiple page redirects Potential savings of 230 ms
Redirects introduce additional delays before the page can be loaded
Avoid chaining critical requests 13 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
Time to Interactive 2.0 s
Time to interactive is the amount of time it takes for the page to become fully 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
First CPU Idle 1.9 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/).
Eliminate render-blocking resources Potential savings of 530 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
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
Properly size images Potential savings of 13 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Avoid non-composited animations 2 animated elements found
Animations which are not composited can be janky and increase CLS
Reduce initial server response time Root document took 700 ms
Keep the server response time for the main document short because all other requests depend on it

Mobile Speed Score

Mobile Screenshot
User Timing marks and measures 3 user timings
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences
Reduce JavaScript execution time 3.3 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Properly size images Potential savings of 26 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Largest Contentful Paint 3.7 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Avoid an excessive DOM size 1,171 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)
Remove unused JavaScript Potential savings of 89 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Reduce the impact of third-party code Third-party code blocked the main thread for 720 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
First Meaningful Paint 3.6 s
First Meaningful Paint measures when the primary content of a page is visible
Time to Interactive 11.1 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Avoid large layout shifts 4 elements found
These DOM elements contribute most to the CLS of the page.
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
Speed Index 5.4 s
Speed Index shows how quickly the contents of a page are visibly populated
Document uses legible font sizes 99.79% 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
Avoid multiple page redirects Potential savings of 780 ms
Redirects introduce additional delays before the page can be loaded
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
Avoid serving legacy JavaScript to modern browsers Potential savings of 12 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers
Keep request counts low and transfer sizes small 128 requests • 959 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Avoids enormous network payloads Total size was 959 KiB
Large network payloads cost users real money and are highly correlated with long load times
Tap targets are sized appropriately 100% 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
First Contentful Paint 3.6 s
First Contentful Paint marks the time at which the first text or image is painted
Eliminate render-blocking resources Potential savings of 1,830 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Cumulative Layout Shift 0.002
Cumulative Layout Shift measures the movement of visible elements within the viewport
Minimize main-thread work 6.5 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Avoid long main-thread tasks 17 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Defer offscreen images Potential savings of 60 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Initial server response time was short Root document took 260 ms
Keep the server response time for the main document short because all other requests depend on it
First Contentful Paint (3G) 7020 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
Serve static assets with an efficient cache policy 19 resources found
A long cache lifetime can speed up repeat visits to your page
Some third-party resources can be lazy loaded with a facade 1 facade alternative available
Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
Enable text compression Potential savings of 7 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
First CPU Idle 10.3 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/).
Avoid chaining critical requests 14 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
Total Blocking Time 1,560 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Max Potential First Input Delay 620 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Estimated Input Latency 190 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

Speed And Optimization Tips

Website speed has a huge impact on performance, affecting user experience, conversion rates and even rankings. ‪‬‬By reducing page load-times, users are less likely to get distracted and the search engines are more likely to reward you by ranking you
Title Website
Congratulations! Your title is optimized
Description Website
Congratulations! Your description is optimized
Robots.txt
Congratulations! Your site have a robots.txt file
Sitemap.xml
Congratulations! We've found a sitemap file for your website
SSL Secure
Warning! Your website is not SSL secured (HTTPS).
Headings
Congratulations! You are using your H1 and H2 tags in your site
Blacklist
Congratulations! Your site is not listed in a blacklist
W3C Validator
Warning! Your site have errors W3C
Accelerated Mobile Pages (AMP)
Warning! Your site not have AMP Version
Domain Authority
Congratulations! Your Domain Authority is good
GZIP Compress
Warning! Your site not is compressed, this can make slower response for the visitors
Favicon
Congratulations! Your website appears to have a favicon.
Broken Links
Congratulations! You not have broken links View links

semrush.com Alexa Rank

1,278

Global Rank

384

India

Domain Available

Domain (TDL) and Typo Status
semrush.co Available Buy Now!
semrush.us Available Buy Now!
semrush.com Available Buy Now!
semrush.org Available Buy Now!
semrush.net Available Buy Now!
smrush.com Available Buy Now!
wemrush.com Available Buy Now!
xemrush.com Available Buy Now!

Information Server semrush.com

Response Header HTTP headers carry information about the client browser, the requested page and the server
HTTP/2 301 
server: nginx
date: Tue, 13 Apr 2021 09:54:32 GMT
content-type: text/html
content-length: 162
location: https://www.semrush.com/
x-xss-protection: 1; mode=block
x-content-type-options: nosniff
strict-transport-security: max-age=31536000; includeSubdomains; preload
x-frame-options: SAMEORIGIN
sm-log-id: flb-17e726ca641cb929d4c7fc00aa31eef6
via: 1.1 google
set-cookie: GCLB=CKTAvuS79_2GOw; path=/; HttpOnly; expires=Wed, 14-Apr-2021 09:54:32 GMT
alt-svc: clear
DNS Records DNS Resource Records associated with a hostname
semrush.com View DNS Records

Social Data