Tools & Wizards About Us
dunnaspark.com.br screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

dunnaspark.com.br

Hotel Dunnas Park | Natal - RN

Page Load Speed

17.6 sec in total

First Response

3.9 sec

Resources Loaded

13.6 sec

Page Rendered

138 ms

dunnaspark.com.br screenshot

About Website

Welcome to dunnaspark.com.br homepage info - get ready to check Dunnas Park best content right away, or after learning these important things about dunnaspark.com.br

Situado a 5 km da Arena das Dunas e a 12 km do Forte dos Reis Magos, o DUNNAS PARK HOTEL oferece acomodação em Natal.

Visit dunnaspark.com.br

Key Findings

We analyzed Dunnaspark.com.br page load time and found that the first response time was 3.9 sec and then it took 13.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

dunnaspark.com.br performance score

0

Network Requests Diagram

3875 ms

wp-emoji-release.min.js

601 ms

styles.css

181 ms

theme-styles.min.css

569 ms

pe-line-icons.min.css

193 ms

Our browser made a total of 47 requests to load all elements on the main page. We found that 87% of them (41 requests) were addressed to the original Dunnaspark.com.br, 11% (5 requests) were made to Fonts.gstatic.com and 2% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (5.5 sec) belongs to the original domain Dunnaspark.com.br.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.1 MB (67%)

Content Size

3.1 MB

After Optimization

1.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Dunnaspark.com.br main page is 3.1 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. 40% of websites need less resources to load. Javascripts take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 52.9 kB

  • Original 64.6 kB
  • After minification 63.9 kB
  • After compression 11.7 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 52.9 kB or 82% of the original size.

Image Optimization

-15%

Potential reduce by 113.4 kB

  • Original 751.3 kB
  • After minification 637.9 kB

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. Obviously, Dunnas Park needs image optimization as it can save up to 113.4 kB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-80%

Potential reduce by 972.5 kB

  • Original 1.2 MB
  • After minification 835.7 kB
  • After compression 245.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 972.5 kB or 80% of the original size.

CSS Optimization

-88%

Potential reduce by 970.1 kB

  • Original 1.1 MB
  • After minification 1.0 MB
  • After compression 127.8 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. Dunnaspark.com.br needs all CSS files to be minified and compressed as it can save up to 970.1 kB or 88% of the original size.

Requests Breakdown

Number of requests can be reduced by 30 (79%)

Requests Now

38

After Optimization

8

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

3875 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

601 ms

styles.css

styles.css

181 ms

theme-styles.min.css

theme-styles.min.css

569 ms

pe-line-icons.min.css

pe-line-icons.min.css

193 ms

font-awesome.min.css

font-awesome.min.css

286 ms

icomoon-fonts.min.css

icomoon-fonts.min.css

447 ms

theme-icons.min.css

theme-icons.min.css

292 ms

css

css

25 ms

style.css

style.css

380 ms

custom.css

custom.css

380 ms

js_composer.css

js_composer.css

5547 ms

wpglobus.min.css

wpglobus.min.css

282 ms

jquery.js

jquery.js

566 ms

jquery-migrate.min.js

jquery-migrate.min.js

342 ms

head-scripts.js

head-scripts.js

390 ms

utils.min.js

utils.min.js

433 ms

flexslider.css

flexslider.css

369 ms

prettyPhoto.css

prettyPhoto.css

470 ms

jquery.form.min.js

jquery.form.min.js

705 ms

scripts.js

scripts.js

422 ms

core.min.js

core.min.js

463 ms

widget.min.js

widget.min.js

512 ms

tabs.min.js

tabs.min.js

559 ms

comment-reply.min.js

comment-reply.min.js

559 ms

scripts-vendors.js

scripts-vendors.js

1241 ms

smoothscroll.js

smoothscroll.js

602 ms

wpglobus.min.js

wpglobus.min.js

653 ms

jquerytransit.js

jquerytransit.js

654 ms

js_composer_front.js

js_composer_front.js

692 ms

jquery.flexslider-min.js

jquery.flexslider-min.js

747 ms

jquery.prettyPhoto.js

jquery.prettyPhoto.js

1140 ms

theme-styles.min-blessed1.css

theme-styles.min-blessed1.css

876 ms

topo.jpg

topo.jpg

1224 ms

logook.png

logook.png

286 ms

slide1.jpg

slide1.jpg

537 ms

slide2.jpg

slide2.jpg

3572 ms

slide3.jpg

slide3.jpg

488 ms

b.php

b.php

390 ms

cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf

cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf

208 ms

DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf

DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf

210 ms

MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf

MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf

210 ms

k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf

k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf

210 ms

EInbV5DfGHOiMmvb1Xr-honF5uFdDttMLvmWuJdhhgs.ttf

EInbV5DfGHOiMmvb1Xr-honF5uFdDttMLvmWuJdhhgs.ttf

209 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

435 ms

fonts-icomoon.woff

fonts-icomoon.woff

1561 ms

flexslider-icon.woff

flexslider-icon.woff

299 ms

SEO Factors

dunnaspark.com.br SEO score

0

Language and Encoding

  • Language Detected

    PT

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Dunnaspark.com.br can be misinterpreted by Google and other search engines. Our service has detected that Portuguese is used on the page, and it does not match the claimed English language. Our system also found out that Dunnaspark.com.br 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

dunnaspark.com.br

Open Graph description is not detected on the main page of Dunnas Park. 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: