Page Title : Watch Service Center | Marina Bay Watch Company
You have a page title and it does not exceed 70 characters. Well done!
About this SEO factor:
Title is the heading of the webpage. The sentence or string enclosed between html title tag () is the title of your website. Search engines searches for the title of your website and displays title along with your website address on search result. Title is the most important element for both SEO and social sharing. Title should be less than 50 to 60 characters because search engine typically displays this length of string or sentence on search result. A good title can consist the primary keyword, secondary keyword and brand name. For example a fictitious gaming information providing sites title may be like "the future of gaming information is here". A webpage title should contain a proper glimpse of the website. title is important element as an identification of your website for user experience, SEO and social sharing. So have a nice and catching title. Learn more
Meta Description : Professional Watch Service Center for all timepieces, from inexpensive to luxury watches, ranging from a quick battery to an overhaul on a watch.
Your meta description does not exceed 150 characters. It's fine.
About this SEO factor:
Description is the full interpretation of your website content and features. Most often it is a short paragraph that describe what are features and information provided by the website to its visitors. You may consider it a advertising of your website. Although not important for search engine ranking but very important for hits or visits through search engine results. Description should be less than 150 character because search engine shows this length of paragraph on search result. And every page of website should contain an unique description to avoid description duplication. Description is the definition of your website for user experience so form it as complete but short and precise illustration of your website.
Meta keywords are keywords inside Meta tags. Meta keywords are not likely to be used for search engine ranking. the words of title and description can be used as meta keywords. it is a good idea for SEO other than search engine ranking.
Keyword usage is the using of your keywords inside Meta tags and contents of your website. Use keywords that describes your site properly for precise search engine result of your website.
Unique words are uncommon words that reflects your site features and informations. Search engine metrics are not intended to use unique words as ranking factor but it is still useful to get a proper picture of your site contents. Using positive unique words like complete, perfect, shiny, is a good idea user experience.
Stop words are common words like all the preposition, some generic words like download, click me, offer, win etc. since most used keyword may be a slight factor for visitors you are encouraged to use more unique words and less stop words.
The ideal page's ratio of text to HTML code must be lie between 20 to 60%. Because if it is come less than 20% it means you need to write more text in your web page while in case of more than 60% your page might be considered as spam.
1 status is the existence of any content inside h1 tag. Although not important like Meta titles and descriptions for search engine ranking but still a good way to describe your contents in search engine result.
h2 status less important but should be used for proper understanding of your website for visitor.
# If the Joomla site is installed within a folder
# eg www.example.com/joomla/ then the robots.txt file
# MUST be moved to the site root
# eg www.example.com/robots.txt
# AND the joomla folder name MUST be prefixed to all of the
# paths.
# eg the Disallow rule for the /administrator/ folder MUST
# be changed to read
# Disallow: /joomla/administrator/
#
# For more information about the robots.txt standard, see:
# http://www.robotstxt.org/orig.html
#
# For syntax checking, see:
# http://tool.motoricerca.info/robots-checker.phtml
User-agent: *
Disallow: /administrator/
Disallow: /bin/
Disallow: /cache/
Disallow: /cli/
Disallow: /components/
Disallow: /includes/
Disallow: /installation/
Disallow: /language/
Disallow: /layouts/
Disallow: /libraries/
Disallow: /logs/
Disallow: /modules/
Disallow: /plugins/
Disallow: /tmp/
Allow: /components/com_creativeimageslider/assets/images/
Allow: /modules/mod_jbusinessreviews/images/
About this SEO factor:
robots.txt is text file that reside on website root directory and contains the instruction for various robots (mainly search engine robots) for how to crawl and indexing your website for their webpage. robots.txt contains the search bots or others bots name, directory list allowed or disallowed to be indexing and crawling for bots, time delay for bots to crawl and indexing and even the sitemap url. A full access or a full restriction or customized access or restriction can be imposed through robots.txt.
robots.txt is very important for SEO. Your website directories will be crawled and indexed on search engine according to robots.txt instructions. So add a robots.txt file in your website root directory. Write it properly including your content enriched pages and other public pages and exclude any pages which contain sensitive information. Remember robots.txt instruction to restrict access to your sensitive information of your page is not formidable on web page security ground. So do not use it on security purpose. Learn more
Sitemap is a xml file which contain full list of your website urls. It is used to include directories of your websites for crawling and indexing for search engine and access for users. it can help search engine robots for indexing your website more fast and deeply. It is roughly an opposite of robots.txt, You can create a sitemap.xml by various free and paid service or you can write it with proper way (read about how write a sitemap).
Also keep these things in mind:
1) Sitemap must be less than 10 MB (10,485,760 bytes) and can contain maximum 50,000 urls. if you have more uls than this create multiple sitemap files and use a sitemap index file.
2) Put your sitemap in website root directory and add the url of your sitemap in robots.txt.
3) sitemap.xml can be compressed using grip for faster loading.
Broken link: a broken link is an inaccessible link or url of a website. a higher rate of broken links have a negative effect on search engine ranking due to reduced link equity. it also has a bad impact on user experience. There are several reasons for broken link. All are listed below.
1) An incorrect link entered by you.
2) The destination website removed the linked web page given by you. (A common 404 error).
3) The destination website is irreversibly moved or not exists anymore. (Changing domain or site blocked or dysfunctional).
4) User may behind some firewall or alike software or security mechanism that is blocking the access to the destination website.
5) You have provided a link to a site that is blocked by firewall or alike software for outside access. Learn more or Learn more
NoIndex : noindex directive is a meta tag value. noindex directive is for not to show your website on search engine results. You must not set ‘noindex’ as value in meta tags if you want to be your website on search engine result.
By default, a webpage is set to “index.” You should add a <meta name="robots" content="noindex" /> directive to a webpage in the <head> section of the HTML if you do not want search engines to crawl a given page and include it in the SERPs (Search Engine Results Pages).
DoFollow & NoFollow : nofollow directive is a meta tag value. Nofollow directive is for not to follow any links of your website by search engine bots. You must not set ‘nofollow’ as value in meta tags if you want follow your link by search engine bots.
By default, links are set to “follow.” You would set a link to “nofollow” in this way: <a href="http://www.example.com/" rel="nofollow">Anchor Text</a> if you want to suggest to Google that the hyperlink should not pass any link equity/SEO value to the link target.
An SEO friendly link is roughly follows these rules. The url should contain dash as a separator, not to contain parameters and numbers and should be static urls.
To resolve this use these techniques.
1) Replace underscore or other separator by dash, clean url by deleting or replaceing number and parameters.
2) Marge your www and non www urls.
3) Do not use dynamic and related urls. Create an xml sitemap for proper indexing of search engine.
4) Block unfriendly and irrelevant links through robots.txt.
5) Endorse your canonical urls in canonical tag. Learn more
An alternate title for image. Alt attribute content to describe an image. It is necessary for notifying search engine spider and improve actability to your website. So put a suitable title for your image at least those are your website content not including the images for designing your website. To resolve this put a suitable title in your alt attributes. Learn more
Older HTML tags and attributes that have been superseded by other more functional or flexible alternatives (whether as HTML or as CSS ) are declared as deprecated in HTML4 by the W3C - the consortium that sets the HTML standards. Browsers should continue to support deprecated tags and attributes, but eventually these tags are likely to become obsolete and so future support cannot be guaranteed.
HTML page size is the one of the main factors of webpage loading time. It should be less than 100 KB according to google recommendation. Note that, this size not including external css, js or images files. So small page size less loading time.
To reduce your page size do this steps
1) Move all your css and js code to external file.
2) make sure your text content be on top of the page so that it can displayed before full page loading.
3) Reduce or compress all the image, flash media file etc. will be better if these files are less than 100 KB Learn more
GZIP is a generic compressor that can be applied to any stream of bytes: under the hood it remembers some of the previously seen content and attempts to find and replace duplicate data fragments in an efficient way - for the curious, great low-level explanation of GZIP. However, in practice, GZIP performs best on text-based content, often achieving compression rates of as high as 70-90% for larger files, whereas running GZIP on assets that are already compressed via alternative algorithms (e.g. most image formats) yields little to no improvement. It is also recommended that, GZIP compressed size should be <=33 KB
Inline css is the css code reside in html page under html tags not in external .css file. Inline css increases the loading time of your webpage which is an important search engine ranking factor. So try not to use inline css.
Internal css is the css codes which resides on html page inside style tag. Internal css is increases loading time since no page caching is possible for internal css. Try to put your css code in external file.
Micro data is the information underlying a html string or paragraph. Consider a string “Avatar”, it could refer a profile picture on forum, blog or social networking site or may it refer to a highly successful 3D movie. Microdot is used to specify the reference or underlying information about an html string. Microdata gives chances to search engine and other application for better understanding of your content and better display significantly on search result. Learn more
If multiple domain name is registered under single ip address the search bots can label other sites as duplicates of one sites. This is ip canonicalization. Little bit like url canonicalizaion. To solve this use redirects. Learn more
Canonical tags make your all urls those lead to a single address or webpage into a single url. Like : <link rel="canonical" href="https://mywebsite.com/home" /> <link rel="canonical" href="https://www.mywebsite.com/home" />
Both refer to the link mywebsite.com/home. So all the different url with same content or page now comes under the link or url mywebsite.com/home. Which will boost up your search engine ranking by eliminating content duplication.
Use canonical tag for all the same urls. Learn more
Site failed plain text email test.4plain text email found.
Plain Text Email List
Info@marinabaywatch.com
Info@marinabaywatch.com
Info@marinabaywatch.com
info@marinabaywatch.com
About this SEO factor:
Plain text email address is vulnerable to email scrapping agents. An email scrapping agent crawls your website and collects every Email address which written in plain text. So existence of plain text email address in your website can help spammers in email Harvesting. This could be a bad sign for search engine.
To fight this you can obfuscate your email addresses in several ways:
1) CSS pseudo classes.
2) Writing backward your email address.
3) Turn of display using css.
4) Obfuscate your email address using javascript.
5) Using wordpress and php (wordpress site only). Learn more
MOBILE
Third-party code blocked the main thread for 50 ms
DESKTOP
Third-party code blocked the main thread for 0 ms
Your third-party code only takes 0.05 seconds. Not terrible.
About this SEO factor:
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. Learn More
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. Learn More
You only have 1 critical request chains. That's good!
About this SEO factor:
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. Learn More
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. Learn More
Your site uses video formats for animated content.
About this SEO factor:
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn More
Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn More
Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn More
Users do not expect a page to refresh automatically, and doing so will move focus back to the top of the page. This may create a frustrating or confusing experience. Learn More
When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn More
If a page doesn't specify a lang attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn More
Form fields with multiple labels can be confusingly announced by assistive technologies like screen readers which use either the first, the last, or all of the labels. Learn More
`[aria-hidden="true"]` elements do not contain focusable descendents
About this SEO factor:
Focusable descendents within an aria-hidden=true element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn More
When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn More
When a toggle field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn More
When a progressbar element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn More
`button`, `link`, and `menuitem` elements have accessible names
About this SEO factor:
When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn More
` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
About this SEO factor:
Screen readers have features to make navigating tables easier. Ensuring table headers always refer to some set of cells may improve the experience for screen reader users. Learn More
When an input field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn More
No element has a `[tabindex]` value greater than 0
About this SEO factor:
A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn More
When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn More
AVOIDS requesting the geolocation permission on page load.
About this SEO factor:
Users are mistrustful of or confused by sites that request their location without context. Consider tying the request to a user action instead. Learn More
The unload event does not fire reliably and listening for it can prevent browser optimizations like the Back-Forward Cache. Consider using the pagehide or visibilitychange events instead. Learn More
AVOIDS requesting the notification permission on page load.
About this SEO factor:
Users are mistrustful of or confused by sites that request to send notifications without context. Consider tying the request to user gestures instead. Learn More
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn More
Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.
A character encoding declaration is required. It can be done with a tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header. Learn More
Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn More
Users do not expect a page to refresh automatically, and doing so will move focus back to the top of the page. This may create a frustrating or confusing experience. Learn More
When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn More
If a page doesn't specify a lang attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn More
Form fields with multiple labels can be confusingly announced by assistive technologies like screen readers which use either the first, the last, or all of the labels. Learn More
`[aria-hidden="true"]` elements do not contain focusable descendents
About this SEO factor:
Focusable descendents within an aria-hidden=true element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn More
When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn More
When a toggle field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn More
When a progressbar element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn More
`button`, `link`, and `menuitem` elements have accessible names
About this SEO factor:
When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn More
` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
About this SEO factor:
Screen readers have features to make navigating tables easier. Ensuring table headers always refer to some set of cells may improve the experience for screen reader users. Learn More
When an input field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn More
No element has a `[tabindex]` value greater than 0
About this SEO factor:
A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn More
When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn More
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed contentLearn More, where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn More
AVOIDS requesting the geolocation permission on page load.
About this SEO factor:
Users are mistrustful of or confused by sites that request their location without context. Consider tying the request to a user action instead. Learn More
The unload event does not fire reliably and listening for it can prevent browser optimizations like the Back-Forward Cache. Consider using the pagehide or visibilitychange events instead. Learn More
NO issues in the `Issues` panel in Chrome Devtools.
About this SEO factor:
Issues logged to the Issues panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.
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. Learn More
Third-party code blocked the main thread for 50 ms
Wasted Miliseconds: 47.876
Wasted Bytes: 21071
Add a <meta name="viewport"> tag to optimize your app for mobile screens. not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn More
Search engines may use href attributes on links to crawl websites. Ensure that the href attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn More
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn More
ID
Label
Selector
More:
Element does not have an alt attribute
aria-label attribute does not exist or is empty
aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty
Element has no title attribute
Element's default semantics were not overridden with role="none" or role="presentation"
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 at least 12px. Learn More
All tap targets ARE sized appropriately. 100% appropriately sized tap targets
About this SEO factor:
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. Learn More
This is a screengrab of what this page looks like on desktop computers.
2 6-4-A
5 6-5-A
6 6-32-DIV
8 6-33-DIV
10 6-6-A
12 6-1-A
14 6-3-A
16 6-12-A
18 6-13-A
19 6-14-A
20 6-9-A
29 6-31-DIV
30 6-7-A
31 6-0-A
32 6-2-A
33 6-8-A
Performance Metrics
The following metrics are generated using performance data.
Overall Performance Score:
1
First Contentful Paint
First Contentful Paint marks the time at which the first text or image is painted onto your page. A good user experience is 0.9s or less.
1.7 s DESKTOP
0.3 s Score: 1Learn More
NA - No data
0.3s
Time to Interactive
Time to interactive is the amount of time it takes for the page to become fully interactive. A good user experience is 2.5s or less.
4.9 s DESKTOP
0.7 s Learn More
Excellent!
0.7s
Speed Index
Speed Index shows how quickly the contents of a page are visibly populated. A good user experience is 1.3s or less.
2.9 s DESKTOP
0.7 s Score: 1Learn More
NA - No data
0.7s
Total Blocking Time
How much time is blocked by scripts during your page loading process or the sum of all time periods between FCP and Time to Interactive. A good user experience is 150ms or less. Learn More
Excellent!
10ms
Largest Contentful Paint
Largest Contentful Paint marks how long it takes for the largest element of content (e.g. a hero image) to be painted on your page. A good user experience is 1.2s or less. Learn more.
Excellent!
0.4s
Cumulative Layout Shift
Cumulative Layout Shift measures the movement of visible elements within the viewport or how much your page's layout shifts as it loads. A good user experience is a score of 0.1 or less. Learn More
NA - No data
0
Total Page Size - 548.8 KB
IMG 198.9 KB
Images
198.9 KB Size36.25% of Total Page Size
Font 155.3 KB
Fonts
155.3 KB Size28.30% of Total Page Size
JS 128.0 KB
JavaScript
128.0 KB Size23.33% of Total Page Size
CSS 55.7 KB
CSS Stylesheets
55.7 KB Size10.15% of Total Page Size
HTML
10.2 KB Size1.86% of Total Page Size
Other
620 B Size0.11% of Total Page Size
Media
0 B Size0.00% of Total Page Size
Total Page Requests - 16
IMG 37.50%
Images
6 Requests37.50% of Total Page Requests
Font 31.25%
Fonts
5 Requests31.25% of Total Page Requests
JS 12.50%
JavaScript
2 Requests12.50% of Total Page Requests
CSS 6.25%
CSS Stylesheets
1 Requests6.25% of Total Page Requests
HTML 6.25%
HTML
1 Requests6.25% of Total Page Requests
Other 6.25%
Other
1 Requests6.25% of Total Page Requests
Video 0.00%
Media
0 Requests0.00% of Total Page Requests
HTML
JS
CSS
IMG
Video
Font
Other
Response Codes:
Response Code
Responses
200
20
Lab Data
First Meaningful Paint
1.8 s
DESKTOP
0.3 s
ID:
first-meaningful-paint
Title:
First Meaningful Paint
Description:
First Meaningful Paint measures when the primary content of a page is visible. [Learn more](https://web.dev/first-meaningful-paint/).
Score:
1
Score Display Mode:
numeric
Display Value:
0.3 s
Numeric Value:
252
Max Potential First Input Delay
490 ms
DESKTOP
70 ms
Audits - Max-Potential FID
ID:
max-potential-fid
Title:
Max Potential First Input Delay
Description:
The maximum potential First Input Delay that your users could experience is the duration of the longest task. [Learn more](https://web.dev/lighthouse-max-potential-fid/).
Score:
0.99
Score Display Mode:
numeric
Display Value:
70 ms
Numeric Value:
70
Audits - Uses Long Cache TTL
Serve static assets with an efficient cache policy
A long cache lifetime can speed up repeat visits to your page. Learn more
Score:
0.88
6 resources found
SI (Speed Index) MS 15%:
721
LCP (Largest Contentful Paint) MS 25%:
390
TTI (Time to Interactive) MS 15%:
700
TBT (Total Blocking Time) MS 25%:
10
CLS (Cumulative Layout Shift) MS 5%:
0
ID:
third-party-summary
Title:
Minimize third-party usage
Description:
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. [Learn more](https://developers.google.com/web/fundamentals/performance/optimizing-content-efficiency/loading-third-party-javascript/).
Score:
1
Score Display Mode:
binary
Display Value:
Third-party code blocked the main thread for 0 ms
Item Detail: Text: Google Analytics URL: https://marketingplatform.google.com/about/analytics/ Type: link Main Thread Time: 31.678 Transfer Size: 21071 Blocking Time: 0
Type:
table
Wasted Bytes:
21071
Wasted Time (ms):
0
Text:
Third-Party
Item Type:
link
Key:
entity
Key:
transferSize
Text:
Transfer Size
Granularity:
1
Item Type:
bytes
Key:
blockingTime
Text:
Main-Thread Blocking Time
Granularity:
1
Item Type:
ms
Audits - Timing Budget
ID:
timing-budget
Title:
Timing budget
Description:
Set a timing budget to help you keep an eye on the performance of your site. Performant sites load fast and respond to user input events quickly. [Learn more](https://developers.google.com/web/tools/lighthouse/audits/budgets).
Score:
Unknown
Score Display Mode:
notApplicable
Audits - Render Blocking Resources
ID:
render-blocking-resources
Title:
Eliminate render-blocking resources
Description:
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. [Learn more](https://web.dev/render-blocking-resources/).
Score:
1
Score Display Mode:
numeric
Display Value:
Unknown
Numeric Value:
0
Type:
opportunity
Overall Savings (ms):
0
Audits - Render Blocking Resources - Details
Audits - Render Blocking Resources - Headings
Audits - Main Thread Tasks
ID:
main-thread-tasks
Title:
Tasks
Description:
Lists the toplevel main thread tasks that executed during page load.
Score:
Unknown
Score Display Mode:
informative
Type:
table
Audits - Main Thread Tasks - Headings
Heading Items: Text: Start Time Key: startTime Item Type: ms Granularity: 1 Heading Items: Text: End Time Key: duration Item Type: ms Granularity: 1
Audits - Network RTT
ID:
network-rtt
Title:
Network Round Trip Times
Description:
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. [Learn more](https://hpbn.co/primer-on-latency-and-bandwidth/).
Score:
Unknown
Score Display Mode:
informative
Display Value:
0 ms
Numeric Value:
0
ID:
interactive
Title:
Time to Interactive
Description:
Time to interactive is the amount of time it takes for the page to become fully interactive. [Learn more](https://web.dev/interactive/).
Score:
1
Score Display Mode:
numeric
Display Value:
0.7 s
Numeric Value:
700
Audits - Critical Request Chains
ID:
critical-request-chains
Title:
Avoid chaining critical requests
Description:
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. [Learn more](https://web.dev/critical-request-chains/).
Score:
Unknown
Score Display Mode:
informative
Display Value:
1 chain found
Longest Chain Transfer Size:
78126
Longest Chain Duration:
940.52199996077
Longest Chain Length:
2
Type:
criticalrequestchain
Audits - Critical Request Chains - Details
Critical Request Chains Request: Request Start Time: 477223.970741 Request Response Received Time: 477224.377738 Request End Time: 477224.377747 Request URL: https://www.marinabaywatch.com/ Request Transfer Size: 10447 Critical Request Chains Children: Critical Request Chains Child: request startTime: 477224.419547 Request Response Received Time: 477224.911257 Request End Time: 477224.911263 Request URL: https://www.marinabaywatch.com/media/gantry5/assets/fonts/fontawesome-webfont.woff2?v=4.7.0 Request Transfer Size: 78126
Audits - Final Screenshot
ID:
final-screenshot
Title:
Final Screenshot
Description:
The last screenshot captured of the pageload.
Score:
Unknown
Score Display Mode:
informative
Type:
screenshot
Timing:
2074
Timestamp:
477226043528
Data:
Audits - Offscreen Images
ID:
offscreen-images
Title:
Defer offscreen images
Description:
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. [Learn more](https://web.dev/offscreen-images/).
Score:
1
Score Display Mode:
numeric
Numeric Value:
0
Overall Savings (ms):
0
Overall Savings Bytes:
0
Type:
opportunity
Audits - Largest Contentful Paint
ID:
largest-contentful-paint
Title:
Largest Contentful Paint
Description:
Largest Contentful Paint marks the time at which the largest text or image is painted. [Learn more](https://web.dev/lighthouse-largest-contentful-paint/)
Score:
1
Score Display Mode:
numeric
Display Value:
0.4 s
Numeric Value:
390
Diagnostics Items: Total Byte Weight: 561978 Max RTT: 0.0040973214103671 Throughput: 36851034686.672 Num Tasks Over 10ms: 9 Num Tasks Over 500ms: 0 Total Task Time: 405.63 Num Tasks: 403 Num Tasks Over 100ms: 0 Num Tasks Over 50ms: 1 RTT: 0.0040973214103671 Num Tasks Over 25ms: 4 Num Stylesheets: 1 Num Scripts: 2 Main Document Transfer Size: 10447 Num Requests: 20 Num Fonts: 5
ID:
resource-summary
Title:
Keep request counts low and transfer sizes small
Description:
To set budgets for the quantity and size of page resources, add a budget.json file. [Learn more](https://web.dev/use-lighthouse-for-performance-budgets/).
Score:
Unknown
Score Display Mode:
informative
Display Value:
16 requests • 549 KiB
Type:
table
Resource Summary Items: Resource Type: total Label: Total Request Count: 16 Transfer Size: 561978 Resource Summary Items: Resource Type: image Label: Image Request Count: 6 Transfer Size: 203704 Resource Summary Items: Resource Type: font Label: Font Request Count: 5 Transfer Size: 159024 Resource Summary Items: Resource Type: script Label: Script Request Count: 2 Transfer Size: 131120 Resource Summary Items: Resource Type: stylesheet Label: Stylesheet Request Count: 1 Transfer Size: 57063 Resource Summary Items: Resource Type: document Label: Document Request Count: 1 Transfer Size: 10447 Resource Summary Items: Resource Type: other Label: Other Request Count: 1 Transfer Size: 620 Resource Summary Items: Resource Type: media Label: Media Request Count: 0 Transfer Size: 0 Resource Summary Items: Resource Type: third-party Label: Third-party Request Count: 2 Transfer Size: 21071
Audits - Server Response Time
ID:
server-response-time
Title:
Initial server response time was short
Description:
Keep the server response time for the main document short because all other requests depend on it. [Learn more](https://web.dev/time-to-first-byte/).
Score:
1
Score Display Mode:
binary
Display Value:
Root document took 410 ms
Numeric Value:
407.997
Type:
opportunity
Overall Savings (ms):
307.997
Audits - Font Display
ID:
font-display
Title:
All text remains visible during webfont loads
Description:
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. [Learn more](https://web.dev/font-display/).
Score:
1
Score Display Mode:
binary
Type:
table
Headings (print_r):
Array
(
)
Items (print_r):
Array
(
)
Audits - Bootup Time
ID:
bootup-time
Title:
JavaScript execution time
Description:
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. [Learn more](https://web.dev/bootup-time/).
Score:
1
Score Display Mode:
numeric
Display Value:
0.1 s
Numeric Value:
134.822
Type:
table
Wasted Time (ms):
134.822
ID:
efficient-animated-content
Title:
Use video formats for animated content
Description:
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. [Learn more](https://web.dev/efficient-animated-content/)
Score:
1
Score Display Mode:
numeric
Numeric Value:
0
Type:
opportunity
Overall Savings Bytes:
0
Overall Savings (ms):
0
Headings (print_r):
Array
(
)
Items (print_r):
Array
(
)
Audits - Metrics
ID:
metrics
Title:
Metrics
Description:
Collects all available metrics.
Score:
Unknown
Score Display Mode:
informative
Numeric Value:
700
Type:
debugdata
Speed Index:
721
Observed First Meaningful Paint (ts):
477224495030
First Meaningful Paint:
252
Observed First Contentful Paint:
526
Observed Navigation Start (ts):
477223969070
Cumulative Layout Shift:
1.4114350757377E-6
Observed Largest Contentful Paint:
843
Observed Trace End (ts):
477227997173
Observed Dom Content Loaded:
444
Observed Cumulative Layout Shift:
1.4114350757377E-6
Observed Dom Content Loaded (ts):
477224413495
Largest Contentful Paint:
390
Observed First Visual Change (ts):
477224476070
Observed Speed Index:
1042
Observed Last Visual Change (ts):
477226043070
Observed Largest Contentful Paint (ts):
477224811973
Max Potential FID:
70
Observed Navigation Start:
0
Observed Last Visual Change:
2074
Observed First Paint:
526
Estimated Input Latency:
Unknown
Observed Load (ts):
477225684219
First Contentful Paint:
252
Observed Speed Index (ts):
477225011236
Observed First Meaningful Paint:
526
Total Blocking Time:
10
Observed Load:
1715
Observed First Contentful Paint (ts):
477224495030
First CPU Idle:
Unknown
Observed First Paint (ts):
477224495030
Observed Trace End:
4028
Interactive:
700
Observed First Visual Change:
507
LCP Invalidated:
Audits - Total Blocking Time
ID:
total-blocking-time
Title:
Total Blocking Time
Description:
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. [Learn more](https://web.dev/lighthouse-total-blocking-time/).
Score:
1
Score Display Mode:
numeric
Display Value:
10 ms
Numeric Value:
10
Audits - Uses Text Compression
ID:
uses-text-compression
Title:
Enable text compression
Description:
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. [Learn more](https://web.dev/uses-text-compression/).
Score:
1
Score Display Mode:
numeric
Numeric Value:
0
Overall Savings (ms):
0
Type:
opportunity
Overall Savings Bytes:
0
Headings (print_r):
Array
(
)
Items (print_r):
Array
(
)
Audits - Total Byte Weight
ID:
total-byte-weight
Title:
Avoids enormous network payloads
Description:
Large network payloads cost users real money and are highly correlated with long load times. [Learn more](https://web.dev/total-byte-weight/).
Score:
1
Score Display Mode:
numeric
Display Value:
Total size was 549 KiB
Numeric Value:
561978
Type:
table
Audits - Total Byte Weight - Items
Total Byte Weight - Items: Total Bytes: 135730 URL: https://www.marinabaywatch.com/images/Watch_Service_Center_Photo.jpg Total Byte Weight - Items: Total Bytes: 110669 URL: https://www.marinabaywatch.com/media/com_jchoptimize/cache/js/fc49fbe7e642206a6c88d7ab399da3ca.js Total Byte Weight - Items: Total Bytes: 78126 URL: https://www.marinabaywatch.com/media/gantry5/assets/fonts/fontawesome-webfont.woff2?v=4.7.0 Total Byte Weight - Items: Total Bytes: 57063 URL: https://www.marinabaywatch.com/media/com_jchoptimize/cache/css/9b3fedd22fca9669354d7c09189cafbb.css Total Byte Weight - Items: Total Bytes: 29735 URL: https://www.marinabaywatch.com/images/jch-optimize/ng/images_header__img.webp Total Byte Weight - Items: Total Bytes: 28718 URL: https://www.marinabaywatch.com/images/shutterstock_439256311.jpg Total Byte Weight - Items: Total Bytes: 20489 URL: https://www.marinabaywatch.com/templates/rt_ambrosia/fonts/robotocondensed/robotocondensed_regular/robotocondensed-regular-webfont.woff2 Total Byte Weight - Items: Total Bytes: 20451 URL: https://www.google-analytics.com/analytics.js Total Byte Weight - Items: Total Bytes: 20259 URL: https://www.marinabaywatch.com/templates/rt_ambrosia/fonts/robotocondensed/robotocondensed_bold/robotocondensed-bold-webfont.woff2 Total Byte Weight - Items: Total Bytes: 20232 URL: https://www.marinabaywatch.com/templates/rt_ambrosia/fonts/roboto/roboto_regular/roboto-regular-webfont.woff2
Audits - Unused Javascript
ID:
unused-javascript
Title:
Reduce unused JavaScript
Description:
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. [Learn more](https://web.dev/unused-javascript/).
Score:
0.93
Score Display Mode:
numeric
Display Value:
Potential savings of 57 KiB
Numeric Value:
80
Type:
opportunity
Overall Savings (ms):
80
Overall Savings Bytes:
58194
Avoid serving legacy JavaScript to modern browsers
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. Score: 1
URL
wastedBytes
0.00 KB
Image elements have explicit `width` and `height`
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Score: 1 1
Image URL
Selector
Avoids enormous network payloads
Large network payloads cost users real money and are highly correlated with long load times. Score: 1
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.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. Score: 1
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Score: 0.93 Potential savings of 57 KiB
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Score: 1
Type
Time Spent
1
Script Evaluation
159.40 MS
2
Other
115.10 MS
3
Style & Layout
72.38 MS
4
Parse HTML & CSS
26.81 MS
5
Rendering
23.80 MS
6
Script Parsing & Compilation
8.14 MS
Avoid multiple page redirects
Redirects introduce additional delays before the page can be loaded. Score: 1 No improvement needed.
Resource Summary
Keep request counts low and transfer sizes small. To set budgets for the quantity and size of page resources, add a budget.json file. 16 requests • 549 KiB
Resource Type
Requests
Transfer Size
1
Image
6
198.93 KB
2
Font
5
155.30 KB
3
Script
2
128.05 KB
4
Stylesheet
1
55.73 KB
5
Document
1
10.20 KB
6
Other
1
0.61 KB
7
Media
0
0.00 KB
8
Third-party
2
20.58 KB
16
549.00 KB
Minify CSS
Minifying CSS files can reduce network payload sizes. Score: 1 No improvement needed.
Eliminate render-blocking resources
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Score: 1 No improvement needed.
Serve images in next-gen formats
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Score: 0.97 Potential savings of 84 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Score: 1 No improvement needed.
Avoid chaining critical requests
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Score: 1 chain found