Tools & Wizards About Us
dubllywood.in screenshot

Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 97

    SEO

    Google-friendlier than
    91% of websites

dubllywood.in

Page Load Speed

9.7 sec in total

First Response

1 sec

Resources Loaded

8.2 sec

Page Rendered

524 ms

dubllywood.in screenshot

About Website

Visit dubllywood.in now to see the best up-to-date Dubllywood content and also check out these interesting facts you probably never knew about dubllywood.in

Dubllywood is an Online Database of Information Related to Mobile Product Content.

Visit dubllywood.in

Key Findings

We analyzed Dubllywood.in page load time and found that the first response time was 1 sec and then it took 8.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

dubllywood.in performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

21/100

10%

LCP (Largest Contentful Paint)

Value11.7 s

0/100

25%

SI (Speed Index)

Value10.6 s

7/100

10%

TBT (Total Blocking Time)

Value4,170 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.108

87/100

15%

TTI (Time to Interactive)

Value13.4 s

11/100

10%

Network Requests Diagram

dubllywood.in

1030 ms

wp-emoji-release.min.js

508 ms

style.min.css

544 ms

styles.css

154 ms

kk-star-ratings.min.css

535 ms

Our browser made a total of 69 requests to load all elements on the main page. We found that 91% of them (63 requests) were addressed to the original Dubllywood.in, 3% (2 requests) were made to Googletagmanager.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Dubllywood.in.

Page Optimization Overview & Recommendations

Page size can be reduced by 113.7 kB (20%)

Content Size

580.5 kB

After Optimization

466.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Dubllywood.in main page is 580.5 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 65% of websites need less resources to load. Images take 217.2 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 85.3 kB

  • Original 102.0 kB
  • After minification 98.7 kB
  • After compression 16.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 85.3 kB or 84% of the original size.

Image Optimization

-9%

Potential reduce by 19.7 kB

  • Original 217.2 kB
  • After minification 197.5 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. Dubllywood images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 2.4 kB

  • Original 140.0 kB
  • After minification 140.0 kB
  • After compression 137.7 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

-5%

Potential reduce by 6.4 kB

  • Original 121.2 kB
  • After minification 121.2 kB
  • After compression 114.9 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. Dubllywood.in has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 26 (39%)

Requests Now

67

After Optimization

41

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

dubllywood.in

dubllywood.in

1030 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

508 ms

style.min.css

style.min.css

544 ms

styles.css

styles.css

154 ms

kk-star-ratings.min.css

kk-star-ratings.min.css

535 ms

style.css

style.css

536 ms

css

css

180 ms

style.css

style.css

817 ms

td_legacy_main.css

td_legacy_main.css

877 ms

td_standard_pack_main.css

td_standard_pack_main.css

1423 ms

tdb_main.css

tdb_main.css

1032 ms

jquery.min.js

jquery.min.js

1183 ms

jquery-migrate.min.js

jquery-migrate.min.js

936 ms

js

js

150 ms

adsbygoogle.js

adsbygoogle.js

169 ms

flexslider.css

flexslider.css

1187 ms

public.css

public.css

1173 ms

index.js

index.js

1612 ms

index.js

index.js

1613 ms

kk-star-ratings.min.js

kk-star-ratings.min.js

1614 ms

underscore.min.js

underscore.min.js

1614 ms

js_posts_autoload.min.js

js_posts_autoload.min.js

1680 ms

tagdiv_theme.min.js

tagdiv_theme.min.js

2277 ms

comment-reply.min.js

comment-reply.min.js

1800 ms

js_files_for_front.min.js

js_files_for_front.min.js

2070 ms

jquery.flexslider.min.js

jquery.flexslider.min.js

2073 ms

jQuery.easing.min.js

jQuery.easing.min.js

2074 ms

Picsart_22-06-15_16-01-49-197-scaled.webp

Picsart_22-06-15_16-01-49-197-scaled.webp

1223 ms

Below-%E2%82%B95000.webp

Below-%E2%82%B95000.webp

1222 ms

Between-%E2%82%B95000-%E2%82%B910000.webp

Between-%E2%82%B95000-%E2%82%B910000.webp

1224 ms

Between-%E2%82%B910000-%E2%82%B915000.png

Between-%E2%82%B910000-%E2%82%B915000.png

1650 ms

Between-%E2%82%B915000-%E2%82%B920000.webp

Between-%E2%82%B915000-%E2%82%B920000.webp

1274 ms

Between-%E2%82%B920000-%E2%82%B925000.webp

Between-%E2%82%B920000-%E2%82%B925000.webp

1509 ms

Above-%E2%82%B925000.webp

Above-%E2%82%B925000.webp

1665 ms

analytics.js

analytics.js

51 ms

js

js

108 ms

newspaper.woff

newspaper.woff

1554 ms

collect

collect

191 ms

bg_direction_nav.png

bg_direction_nav.png

506 ms

admin-ajax.php

admin-ajax.php

1014 ms

iQOO-Neo-6-5G-324x160.webp

iQOO-Neo-6-5G-324x160.webp

473 ms

Redmi-A1-324x160.webp

Redmi-A1-324x160.webp

462 ms

Tecno-POP-6-Pro-324x160.webp

Tecno-POP-6-Pro-324x160.webp

441 ms

iQOO-Z6-44W-324x160.webp

iQOO-Z6-44W-324x160.webp

242 ms

Redmi-K50i-5G-324x160.webp

Redmi-K50i-5G-324x160.webp

435 ms

OnePlus-Nord-CE-2-5G-324x160.webp

OnePlus-Nord-CE-2-5G-324x160.webp

682 ms

Redmi-11-Prime-5G-324x160.webp

Redmi-11-Prime-5G-324x160.webp

756 ms

Samsung-Galaxy-M53-5G-324x160.webp

Samsung-Galaxy-M53-5G-324x160.webp

901 ms

Samsung-Galaxy-M33-5G-324x160.webp

Samsung-Galaxy-M33-5G-324x160.webp

885 ms

Redmi-10A_copy_400x225-324x160.webp

Redmi-10A_copy_400x225-324x160.webp

932 ms

Samsung-Galaxy-M32-324x160.webp

Samsung-Galaxy-M32-324x160.webp

987 ms

OPPO-A31-324x160.webp

OPPO-A31-324x160.webp

952 ms

iQOO-Neo-6-5G-324x160.webp

iQOO-Neo-6-5G-324x160.webp

556 ms

iQOO-Z6-44W-324x160.webp

iQOO-Z6-44W-324x160.webp

548 ms

Picsart_22-06-04_10-34-04-086_copy_1025x525-324x160.webp

Picsart_22-06-04_10-34-04-086_copy_1025x525-324x160.webp

650 ms

Picsart_22-06-02_08-26-25-059_copy_1025x525-324x160.webp

Picsart_22-06-02_08-26-25-059_copy_1025x525-324x160.webp

676 ms

Picsart_22-05-31_10-10-40-302_copy_1025x525-324x160.webp

Picsart_22-05-31_10-10-40-302_copy_1025x525-324x160.webp

726 ms

Picsart_22-05-29_10-38-41-008_copy_887x454-324x160.webp

Picsart_22-05-29_10-38-41-008_copy_887x454-324x160.webp

778 ms

Picsart_22-05-28_13-28-16-209_copy_887x454_1-324x160.webp

Picsart_22-05-28_13-28-16-209_copy_887x454_1-324x160.webp

933 ms

Picsart_22-05-27_10-40-37-198_copy_887x454-324x160.webp

Picsart_22-05-27_10-40-37-198_copy_887x454-324x160.webp

981 ms

Picsart_22-05-26_08-52-54-683_copy_887x454-324x160.webp

Picsart_22-05-26_08-52-54-683_copy_887x454-324x160.webp

1111 ms

Picsart_22-05-21_11-31-16-245_copy_887x454-324x160.webp

Picsart_22-05-21_11-31-16-245_copy_887x454-324x160.webp

1098 ms

Picsart_22-05-16_12-54-59-644_copy_887x454-324x160.webp

Picsart_22-05-16_12-54-59-644_copy_887x454-324x160.webp

926 ms

Picsart_22-05-15_12-52-10-707_copy_887x454-324x160.webp

Picsart_22-05-15_12-52-10-707_copy_887x454-324x160.webp

1194 ms

Picsart_22-05-13_00-49-16-910_copy_887x454-324x160.webp

Picsart_22-05-13_00-49-16-910_copy_887x454-324x160.webp

1385 ms

Picsart_22-05-12_12-11-03-831_copy_887x454-324x160.webp

Picsart_22-05-12_12-11-03-831_copy_887x454-324x160.webp

1387 ms

Picsart_22-05-10_21-55-13-003_copy_887x454-324x160.webp

Picsart_22-05-10_21-55-13-003_copy_887x454-324x160.webp

1393 ms

Picsart_22-05-09_11-59-44-931_copy_887x454-324x160.webp

Picsart_22-05-09_11-59-44-931_copy_887x454-324x160.webp

1315 ms

Picsart_22-05-08_11-41-29-431_copy_887x454-324x160.webp

Picsart_22-05-08_11-41-29-431_copy_887x454-324x160.webp

1580 ms

Accessibility Review

dubllywood.in accessibility score

93

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-hidden="true"] elements contain focusable descendents

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.

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

Links do not have a discernible name

Best Practices

dubllywood.in best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

dubllywood.in SEO score

97

Search Engine Optimization Advices

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

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Dubllywood.in can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Dubllywood.in 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

dubllywood.in

Open Graph data is detected on the main page of Dubllywood. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: