Your Website Score is
SEO Rank : 4 Website URL: pratyashatripura.in Last Updated: 2 months
Success
39% of passed verification steps
Warning
23% of total warning
Errors
38% of total errors, require fast action
Share
Estimation Traffic and Earnings
0
Unique Visits
Daily
0
Pages Views
Daily
$0
Income
Daily
0
Unique Visits
Monthly
0
Pages Views
Monthly
$0
Income
Monthly
0
Unique Visits
Yearly
0
Pages Views
Yearly
$0
Income
Yearly
Desktop
Mobile
Moz Authority Rank
Page Authority
Authority 17%
Domain Authority
Domain Authority 4%
Moz Rank
1.7/10
Bounce Rate
Rate 0%
Meta Data
Charset
Encoding
Great, language/character encoding is specified: UTF-8
Title Tag
43 Characters
HOME | PRATYASHA TRIPURA EVENING DAILY NEWS
Meta Description
76 Characters
Pratyasha tripura is a daily evening bengali newspaper in Agartala, Tripura.
Effective URL
27 Characters
https://pratyashatripura.in
Excerpt
Page content
Home | Pratyasha Tripura Evening Daily News
Tel: 0381-2383608 | Mail: [email protected]
HOME
ABOUT US
CONTACT
PAGE 1
PAGE 2
PAGE 3
PAGE 4
Developed By :
Privacy Policy
Meta Keywords
5 Detected
Google Preview
Your look like this in google search result
HOME | PRATYASHA TRIPURA EVENING DAILY NEWS
https://pratyashatripura.in
Pratyasha tripura is a daily evening bengali newspaper in Agartala, Tripura.
Robots.txt
File No Found
Sitemap.xml
File No Found
Page Size
Code & Text Ratio
Document Size: ~4.51 KB
Code Size: ~3.81 KB
Text Size: ~714 B Ratio: 15.47%
Social Data
Delicious
Total: 0
Facebook
Total: 0
Google
Total: 0
Linkedin
Total: 0
Pinterest
Total: 0
Stumbleupon
Total: 0
Tumblr
Total: 0
Vk
Total: 0
Technologies
PWA - Manifest
Manifest is not valid
Your site don't have valid manifest.json, read more in Web App Manifest
Desktop
Avoid chaining critical requests
5 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
Minimizes main-thread work
1.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 13 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
JavaScript execution time
0.5 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Serve images in next-gen formats
Potential savings of 60 KiB
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
Total Blocking Time
90 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Reduce initial server response time
Root document took 720 ms
Keep the server response time for the main document short because all other requests depend on it
Time to Interactive
2.1 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Avoid serving legacy JavaScript to modern browsers
Potential savings of 23 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
Avoids an excessive DOM size
64 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)
Minimize third-party usage
Third-party code blocked the main thread for 100 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
Avoids large JavaScript libraries with smaller alternatives
0 large libraries found
Large JavaScript libraries can lead to poor performance. Prefer smaller, functionally equivalent libraries to reduce your bundle size
Serve static assets with an efficient cache policy
6 resources found
A long cache lifetime can speed up repeat visits to your page
First Meaningful Paint
0.5 s
First Meaningful Paint measures when the primary content of a page is visible
Largest Contentful Paint
2.7 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Largest Contentful Paint element
1 element found
This is the largest contentful element painted within the viewport
Includes front-end JavaScript libraries with known security vulnerabilities
2 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Remove unused JavaScript
Potential savings of 352 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Speed Index
2.3 s
Speed Index shows how quickly the contents of a page are visibly populated
Eliminate render-blocking resources
Potential savings of 250 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Avoid long main-thread tasks
2 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Page load is not fast enough on mobile networks
Interactive on simulated mobile network at 12.3 s
A fast page load over a cellular network ensures a good mobile user experience
Estimated Input Latency
20 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
Remove unused CSS
Potential savings of 83 KiB
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
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
Efficiently encode images
Potential savings of 44 KiB
Optimized images load faster and consume less cellular data
Keep request counts low and transfer sizes small
51 requests • 2,126 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
First CPU Idle
2.0 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/).
First Contentful Paint
0.5 s
First Contentful Paint marks the time at which the first text or image is painted
Max Potential First Input Delay
140 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Avoid large layout shifts
5 elements found
These DOM elements contribute most to the CLS of the page.
Avoids enormous network payloads
Total size was 2,126 KiB
Large network payloads cost users real money and are highly correlated with long load times
Mobile
Efficiently encode images
Potential savings of 41 KiB
Optimized images load faster and consume less cellular data
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
Largest Contentful Paint element
1 element found
This is the largest contentful element painted within the viewport
Document doesn't use legible font sizes
0.34% 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
Largest Contentful Paint
4.4 s
Largest Contentful Paint marks the time at which the largest text or image is painted
First Meaningful Paint
2.6 s
First Meaningful Paint measures when the primary content of a page is visible
Preload key requests
Potential savings of 480 ms
Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load
Avoid serving legacy JavaScript to modern browsers
Potential savings of 30 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
Reduce initial server response time
Root document took 730 ms
Keep the server response time for the main document short because all other requests depend on it
Speed Index
7.2 s
Speed Index shows how quickly the contents of a page are visibly populated
Avoid enormous network payloads
Total size was 5,444 KiB
Large network payloads cost users real money and are highly correlated with long load times
Avoid long main-thread tasks
20 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Avoid multiple page redirects
Potential savings of 1,110 ms
Redirects introduce additional delays before the page can be loaded
Remove unused CSS
Potential savings of 84 KiB
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
Avoid large layout shifts
5 elements found
These DOM elements contribute most to the CLS of the page.
Serve images in next-gen formats
Potential savings of 219 KiB
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
First Contentful Paint (3G)
5270 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
Total Blocking Time
870 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Avoids large JavaScript libraries with smaller alternatives
0 large libraries found
Large JavaScript libraries can lead to poor performance. Prefer smaller, functionally equivalent libraries to reduce your bundle size
Time to Interactive
11.2 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Avoids an excessive DOM size
47 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)
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/).
Includes front-end JavaScript libraries with known security vulnerabilities
2 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Max Potential First Input Delay
380 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
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
Reduce JavaScript execution time
2.7 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
First Contentful Paint
2.6 s
First Contentful Paint marks the time at which the first text or image is painted
Keep request counts low and transfer sizes small
58 requests • 5,444 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Cumulative Layout Shift
0.447
Cumulative Layout Shift measures the movement of visible elements within the viewport
Minimize main-thread work
5.3 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Page load is not fast enough on mobile networks
Interactive at 11.2 s
A fast page load over a cellular network ensures a good mobile user experience
Uses efficient cache policy on static assets
8 resources found
A long cache lifetime can speed up repeat visits to your page
Remove unused JavaScript
Potential savings of 488 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 920 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
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
Estimated Input Latency
90 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
Eliminate render-blocking resources
Potential savings of 830 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
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
Warning! Your site not have a robots.txt file
Sitemap.xml
Warning! Not found a sitemap file for your website
SSL Secure
Congratulations! Your site have Support to HTTPS
Headings
Warning! Your page not contain any H1 and H2 headings. H1 and H2 headings help indicate the important topics of your page to search engines
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
Warning! Domain Authority of your website is slow. It is good to have domain authority more than 25.
GZIP Compress
Warning! Your site not is compressed, this can make slower response for the visitors
Favicon
Warning! Your site not have a favicon
Broken Links
Congratulations! You not have broken links
View links
| First 5 Links | Relationship | HTTP Status |
| [email protected] | Internal Link | 200 |
| HOME | Internal Link | 200 |
| ABOUT US | Internal Link | 200 |
| CONTACT | Internal Link | 200 |
| Privacy Policy | Internal Link | 200 |
Alexa Rank
0
Local Rank: / Users: / PageViews:
Global Rank
Domain Available
| Domain (TDL) and Typo | Status |
|---|---|
| pratyashatripura.co | Already Registered |
| pratyashatripura.us | Already Registered |
| pratyashatripura.com | Already Registered |
| pratyashatripura.org | Already Registered |
| pratyashatripura.net | Already Registered |
| patyashatripura.in | Already Registered |
| lratyashatripura.in | Already Registered |
Information Server
Response Header
HTTP headers carry information about the client browser, the requested page and the server
HTTP/2 200
date: Fri, 04 Dec 2020 03:09:51 GMT
content-type: text/html; charset=UTF-8
set-cookie: __cfduid=d114e9e446985febe66cf3a88414a939b1607051391; expires=Sun, 03-Jan-21 03:09:51 GMT; path=/; domain=.pratyashatripura.in; HttpOnly; SameSite=Lax; Secure
cf-ray: 5fc254ba1995ebd9-LAX
cf-cache-status: DYNAMIC
cf-request-id: 06cd53484e0000ebd9640e3000000001
expect-ct: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
report-to: {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report?s=k%2B1gj%2B5x2buHYDXo1XzhEf8wGbphzpLjbcSEBnVGmXJ6gM7UUg0Hm1a8uOox2Rj%2B8vsY61fq7pGqz3%2BS2pWGwS0u3T1wnZDAJAmfi1%2FiN5gmN5B2"}],"group":"cf-nel","max_age":604800}
nel: {"report_to":"cf-nel","max_age":604800}
vary: Accept-Encoding
server: cloudflare
content-encoding: gzip
Click to Add/Show Comments