Tools & Wizards About Us
nadivana.com screenshot

Report Summary

  • 65

    Performance

    Renders faster than
    78% of other websites

  • 65

    Accessibility

    Visual factors better than
    that of 30% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 81

    SEO

    Google-friendlier than
    42% of websites

nadivana.com

Nadivana - fully serviced apartments in a resort setting

Page Load Speed

862 ms in total

First Response

64 ms

Resources Loaded

444 ms

Page Rendered

354 ms

nadivana.com screenshot

About Website

Click here to check amazing Nadivana content. Otherwise, check out these important facts you probably never knew about nadivana.com

Fully serviced 'open plan' studio and two bedrooms luxury poolside apartments. Jacuzzis, swim-up bar, restaurant, massage, room service, minimart and spa.

Visit nadivana.com

Key Findings

We analyzed Nadivana.com page load time and found that the first response time was 64 ms and then it took 798 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

nadivana.com performance score

65

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.8 s

89/100

10%

LCP (Largest Contentful Paint)

Value7.1 s

5/100

25%

SI (Speed Index)

Value2.7 s

96/100

10%

TBT (Total Blocking Time)

Value170 ms

92/100

30%

CLS (Cumulative Layout Shift)

Value0.183

66/100

15%

TTI (Time to Interactive)

Value4.8 s

78/100

10%

Network Requests Diagram

nadivana.com

64 ms

base.css

20 ms

skeleton.css

41 ms

menu.css

39 ms

flexslider.css

41 ms

Our browser made a total of 59 requests to load all elements on the main page. We found that 90% of them (53 requests) were addressed to the original Nadivana.com, 3% (2 requests) were made to Stats.g.doubleclick.net and 2% (1 request) were made to Code.jquery.com. The less responsive or slowest element that took the longest time to load (205 ms) belongs to the original domain Nadivana.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 154.9 kB (2%)

Content Size

6.5 MB

After Optimization

6.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Nadivana.com main page is 6.5 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 6.1 MB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 93.2 kB

  • Original 106.9 kB
  • After minification 105.4 kB
  • After compression 13.6 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 93.2 kB or 87% of the original size.

Image Optimization

-1%

Potential reduce by 40.0 kB

  • Original 6.1 MB
  • After minification 6.0 MB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Nadivana images are well optimized though.

JavaScript Optimization

-5%

Potential reduce by 14.6 kB

  • Original 280.8 kB
  • After minification 280.8 kB
  • After compression 266.2 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. This website has mostly compressed JavaScripts.

CSS Optimization

-40%

Potential reduce by 7.0 kB

  • Original 17.4 kB
  • After minification 17.4 kB
  • After compression 10.4 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Nadivana.com needs all CSS files to be minified and compressed as it can save up to 7.0 kB or 40% of the original size.

Requests Breakdown

Number of requests can be reduced by 12 (21%)

Requests Now

56

After Optimization

44

  • Images
  • JavaScript
  • CSS

The browser has sent 56 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Nadivana. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

nadivana.com

nadivana.com

64 ms

base.css

base.css

20 ms

skeleton.css

skeleton.css

41 ms

menu.css

menu.css

39 ms

flexslider.css

flexslider.css

41 ms

layout.css

layout.css

47 ms

prettyPhoto.css

prettyPhoto.css

45 ms

jquery-1.7.1.min.js

jquery-1.7.1.min.js

6 ms

flexi_slider.js

flexi_slider.js

40 ms

widget.js

widget.js

111 ms

plug_ins.js

plug_ins.js

104 ms

js

js

64 ms

google_map.js

google_map.js

65 ms

functions.js

functions.js

65 ms

dc.js

dc.js

10 ms

bg_header.png

bg_header.png

46 ms

logo_1.gif

logo_1.gif

46 ms

menu_footer_divider.png

menu_footer_divider.png

47 ms

menu_top_divider.png

menu_top_divider.png

47 ms

slider_1.jpg

slider_1.jpg

148 ms

slider_2.jpg

slider_2.jpg

147 ms

slider_3.jpg

slider_3.jpg

149 ms

slider_4.jpg

slider_4.jpg

149 ms

slider_5.jpg

slider_5.jpg

149 ms

slider_6.jpg

slider_6.jpg

147 ms

slider_7.jpg

slider_7.jpg

150 ms

slider_8.jpg

slider_8.jpg

150 ms

slider_9.jpg

slider_9.jpg

152 ms

slider_10.jpg

slider_10.jpg

151 ms

slider_11.jpg

slider_11.jpg

152 ms

slider_12.jpg

slider_12.jpg

153 ms

slider_13.jpg

slider_13.jpg

151 ms

slider_14.jpg

slider_14.jpg

154 ms

slider_15.jpg

slider_15.jpg

154 ms

slider_16.jpg

slider_16.jpg

155 ms

slider_17.jpg

slider_17.jpg

153 ms

slider_18.jpg

slider_18.jpg

155 ms

slider_19.jpg

slider_19.jpg

168 ms

big_shadow.png

big_shadow.png

158 ms

room_1.jpg

room_1.jpg

158 ms

room_2.jpg

room_2.jpg

156 ms

room_3.jpg

room_3.jpg

158 ms

room_4_room_page_2.jpg

room_4_room_page_2.jpg

156 ms

room_5_room_page_2.jpg

room_5_room_page_2.jpg

173 ms

Nadivana%20Pool%20'16.jpg

Nadivana%20Pool%20'16.jpg

205 ms

Maya-Bay.jpg

Maya-Bay.jpg

175 ms

Nadivana%20Krabi%20Resort.jpg

Nadivana%20Krabi%20Resort.jpg

174 ms

spa.jpg

spa.jpg

174 ms

__utm.gif

__utm.gif

103 ms

yql

yql

156 ms

zoom_1.png

zoom_1.png

57 ms

shadow_1.png

shadow_1.png

56 ms

icons_room.png

icons_room.png

60 ms

bg_blue_line.png

bg_blue_line.png

58 ms

divider_2.png

divider_2.png

57 ms

bg_footer.png

bg_footer.png

74 ms

tip-twitter_arrows.gif

tip-twitter_arrows.gif

76 ms

PTN57F-webfont.woff

PTN57F-webfont.woff

70 ms

bg_control_nav.png

bg_control_nav.png

19 ms

Accessibility Review

nadivana.com accessibility score

65

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Form elements do not have associated labels

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

nadivana.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

nadivana.com SEO score

81

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Nadivana.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Nadivana.com main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

nadivana.com

Open Graph description is not detected on the main page of Nadivana. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: