Tools & Wizards About Us
naplesuk.com screenshot

Report Summary

  • 24

    Performance

    Renders faster than
    43% of other websites

  • 65

    Accessibility

    Visual factors better than
    that of 30% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 81

    SEO

    Google-friendlier than
    42% of websites

naplesuk.com

Kitchen Ducting

Page Load Speed

3.4 sec in total

First Response

688 ms

Resources Loaded

2.4 sec

Page Rendered

263 ms

naplesuk.com screenshot

About Website

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

Visit naplesuk.com

Key Findings

We analyzed Naplesuk.com page load time and found that the first response time was 688 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

naplesuk.com performance score

24

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

25/100

10%

LCP (Largest Contentful Paint)

Value4.1 s

46/100

25%

SI (Speed Index)

Value10.1 s

9/100

10%

TBT (Total Blocking Time)

Value1,020 ms

26/100

30%

CLS (Cumulative Layout Shift)

Value0.784

5/100

15%

TTI (Time to Interactive)

Value14.4 s

9/100

10%

Network Requests Diagram

www.naplesuk.com

688 ms

calendar.css

79 ms

styles-m.css

307 ms

owl.carousel.css

235 ms

jquery.fancybox.css

234 ms

Our browser made a total of 76 requests to load all elements on the main page. We found that 78% of them (59 requests) were addressed to the original Naplesuk.com, 9% (7 requests) were made to Fonts.gstatic.com and 7% (5 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (965 ms) belongs to the original domain Naplesuk.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 358.4 kB (18%)

Content Size

2.0 MB

After Optimization

1.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-87%

Potential reduce by 99.2 kB

  • Original 114.6 kB
  • After minification 96.4 kB
  • After compression 15.5 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. This page needs HTML code to be minified as it can gain 18.2 kB, which is 16% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 99.2 kB or 87% of the original size.

Image Optimization

-1%

Potential reduce by 3.9 kB

  • Original 468.4 kB
  • After minification 464.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. Naplesuk images are well optimized though.

JavaScript Optimization

-17%

Potential reduce by 209.5 kB

  • Original 1.2 MB
  • After minification 1.2 MB
  • After compression 1.0 MB

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 209.5 kB or 17% of the original size.

CSS Optimization

-23%

Potential reduce by 45.9 kB

  • Original 197.0 kB
  • After minification 197.0 kB
  • After compression 151.1 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. Naplesuk.com needs all CSS files to be minified and compressed as it can save up to 45.9 kB or 23% of the original size.

Requests Breakdown

Number of requests can be reduced by 41 (64%)

Requests Now

64

After Optimization

23

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 64 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Naplesuk. 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 26 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

www.naplesuk.com

www.naplesuk.com

688 ms

calendar.css

calendar.css

79 ms

styles-m.css

styles-m.css

307 ms

owl.carousel.css

owl.carousel.css

235 ms

jquery.fancybox.css

jquery.fancybox.css

234 ms

porto-icons-codes.css

porto-icons-codes.css

236 ms

simple-line-icons.css

simple-line-icons.css

241 ms

animation.css

animation.css

241 ms

font-awesome.min.css

font-awesome.min.css

323 ms

style.css

style.css

324 ms

scroll.css

scroll.css

325 ms

styles-l.css

styles-l.css

404 ms

all.css

all.css

34 ms

css

css

36 ms

css

css

50 ms

css

css

57 ms

css

css

56 ms

bootstrap.optimized.min.css

bootstrap.optimized.min.css

325 ms

animate.optimized.css

animate.optimized.css

383 ms

type1.css

type1.css

394 ms

custom.css

custom.css

475 ms

design_default.css

design_default.css

399 ms

settings_default.css

settings_default.css

408 ms

whitedemo.css

whitedemo.css

460 ms

logo.jpg

logo.jpg

608 ms

group-1.css

group-1.css

478 ms

require.min.js

require.min.js

604 ms

requirejs-min-resolver.min.js

requirejs-min-resolver.min.js

603 ms

bundle0.min.js

bundle0.min.js

614 ms

bundle1.min.js

bundle1.min.js

801 ms

bundle2.min.js

bundle2.min.js

884 ms

bundle3.min.js

bundle3.min.js

806 ms

bundle4.min.js

bundle4.min.js

730 ms

static.min.js

static.min.js

627 ms

mixins.min.js

mixins.min.js

691 ms

requirejs-config.min.js

requirejs-config.min.js

702 ms

scroll.min.js

scroll.min.js

769 ms

home-slider.min.js

home-slider.min.js

783 ms

paypal-js.min.js

paypal-js.min.js

35 ms

js

js

64 ms

js

js

110 ms

banner1_1458126374.jpg

banner1_1458126374.jpg

965 ms

banner2_1458126384.jpg

banner2_1458126384.jpg

846 ms

banner3_1458126505.jpg

banner3_1458126505.jpg

965 ms

ducting.jpg

ducting.jpg

878 ms

kitchen-handles.jpg

kitchen-handles.jpg

895 ms

kitchen-knobs.jpg

kitchen-knobs.jpg

741 ms

lighting.jpg

lighting.jpg

771 ms

storage-solutions.jpg

storage-solutions.jpg

770 ms

accessories.jpg

accessories.jpg

765 ms

d6alukgt_1.jpg

d6alukgt_1.jpg

765 ms

d6alukgbe_2.jpg

d6alukgbe_2.jpg

707 ms

d6alukgb_2.jpg

d6alukgb_2.jpg

706 ms

d6alukgt.jpg

d6alukgt.jpg

752 ms

image_77.jpg

image_77.jpg

752 ms

d6alukgw.jpg

d6alukgw.jpg

750 ms

image_80.jpg

image_80.jpg

694 ms

ducting-vents.png

ducting-vents.png

697 ms

paypal_logo.png

paypal_logo.png

705 ms

css2

css2

19 ms

loading.gif

loading.gif

636 ms

footer-stripeswhite.png

footer-stripeswhite.png

750 ms

fa-brands-400.woff

fa-brands-400.woff

15 ms

fa-brands-400.woff

fa-brands-400.woff

534 ms

porto-icons.woff

porto-icons.woff

540 ms

pxiByp8kv8JHgFVrLEj6Z1xlEA.ttf

pxiByp8kv8JHgFVrLEj6Z1xlEA.ttf

21 ms

pxiByp8kv8JHgFVrLCz7Z1xlEA.ttf

pxiByp8kv8JHgFVrLCz7Z1xlEA.ttf

22 ms

pxiByp8kv8JHgFVrLDD4Z1xlEA.ttf

pxiByp8kv8JHgFVrLDD4Z1xlEA.ttf

47 ms

pxiByp8kv8JHgFVrLGT9Z1xlEA.ttf

pxiByp8kv8JHgFVrLGT9Z1xlEA.ttf

47 ms

pxiEyp8kv8JHgFVrJJfedw.ttf

pxiEyp8kv8JHgFVrJJfedw.ttf

54 ms

pxiByp8kv8JHgFVrLDz8Z1xlEA.ttf

pxiByp8kv8JHgFVrLDz8Z1xlEA.ttf

53 ms

pxiByp8kv8JHgFVrLFj_Z1xlEA.ttf

pxiByp8kv8JHgFVrLFj_Z1xlEA.ttf

53 ms

text.min.js

text.min.js

216 ms

moment.min.js

moment.min.js

107 ms

js-translation.json

js-translation.json

78 ms

print.css

print.css

78 ms

Accessibility Review

naplesuk.com accessibility score

65

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

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

[role]s are not contained by their required parent element

High

ARIA IDs are not unique

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

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

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

naplesuk.com best practices score

67

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

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

naplesuk.com SEO score

81

Search Engine Optimization Advices

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 Naplesuk.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 Naplesuk.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

naplesuk.com

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