Tools & Wizards About Us
portworks.com screenshot

Report Summary

  • 40

    Performance

    Renders faster than
    59% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 81

    SEO

    Google-friendlier than
    42% of websites

portworks.com

Specializing in After-Dinner Wines

Page Load Speed

1.5 sec in total

First Response

144 ms

Resources Loaded

1 sec

Page Rendered

341 ms

portworks.com screenshot

About Website

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

Nothing says dessert like port wine and sherry. Visit Sonoma County's only winery specializing in port and after-dinner wines.

Visit portworks.com

Key Findings

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

Performance Metrics

portworks.com performance score

40

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

37/100

10%

LCP (Largest Contentful Paint)

Value6.0 s

13/100

25%

SI (Speed Index)

Value7.0 s

32/100

10%

TBT (Total Blocking Time)

Value540 ms

54/100

30%

CLS (Cumulative Layout Shift)

Value0.151

75/100

15%

TTI (Time to Interactive)

Value10.8 s

22/100

10%

Network Requests Diagram

portworks.com

144 ms

portworks.com

289 ms

styles.css

139 ms

style.min.css

178 ms

style.min.css

147 ms

Our browser made a total of 52 requests to load all elements on the main page. We found that 4% of them (2 requests) were addressed to the original Portworks.com, 62% (32 requests) were made to 428741.p3cdn1.secureserver.net and 17% (9 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (377 ms) relates to the external source Shop.portworks.com.

Page Optimization Overview & Recommendations

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

Content Size

2.4 MB

After Optimization

2.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Portworks.com main page is 2.4 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. 75% 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 2.0 MB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 49.0 kB

  • Original 64.3 kB
  • After minification 62.0 kB
  • After compression 15.3 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 49.0 kB or 76% of the original size.

Image Optimization

-0%

Potential reduce by 1.1 kB

  • Original 2.0 MB
  • After minification 1.9 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. Portworks images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 7.9 kB

  • Original 347.1 kB
  • After minification 346.1 kB
  • After compression 339.1 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

-0%

Potential reduce by 220 B

  • Original 82.5 kB
  • After minification 82.5 kB
  • After compression 82.3 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. Portworks.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 28 (70%)

Requests Now

40

After Optimization

12

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

portworks.com

portworks.com

144 ms

portworks.com

portworks.com

289 ms

styles.css

styles.css

139 ms

style.min.css

style.min.css

178 ms

style.min.css

style.min.css

147 ms

css

css

51 ms

style-static.min.css

style-static.min.css

152 ms

jquery.min.js

jquery.min.js

149 ms

jquery-migrate.min.js

jquery-migrate.min.js

147 ms

cp_widget.js

cp_widget.js

65 ms

iframeResizer.min.js

iframeResizer.min.js

62 ms

jquery.min.js

jquery.min.js

34 ms

vin65remotetools.1.1.js

vin65remotetools.1.1.js

54 ms

js

js

75 ms

hooks.min.js

hooks.min.js

175 ms

i18n.min.js

i18n.min.js

207 ms

index.js

index.js

209 ms

index.js

index.js

208 ms

scripts.min.js

scripts.min.js

209 ms

jquery.fitvids.js

jquery.fitvids.js

251 ms

jquery.mobile.js

jquery.mobile.js

245 ms

magnific-popup.js

magnific-popup.js

245 ms

easypiechart.js

easypiechart.js

245 ms

salvattore.js

salvattore.js

246 ms

frontend-bundle.min.js

frontend-bundle.min.js

245 ms

frontend-bundle.min.js

frontend-bundle.min.js

246 ms

new-tab.js

new-tab.js

247 ms

common.js

common.js

296 ms

motion-effects.js

motion-effects.js

246 ms

sticky-elements.js

sticky-elements.js

247 ms

index.cfm

index.cfm

377 ms

widget.js

widget.js

230 ms

SPW_logoV21.png

SPW_logoV21.png

43 ms

Petite-Sirah-and-Petit-Verdot-with-CocoTutti-chocolate-sensual-1-scaled.jpg

Petite-Sirah-and-Petit-Verdot-with-CocoTutti-chocolate-sensual-1-scaled.jpg

46 ms

Valentinos-Delight.jpeg

Valentinos-Delight.jpeg

258 ms

Logo-Corkscrew-2.jpg

Logo-Corkscrew-2.jpg

44 ms

fb-logo.png

fb-logo.png

89 ms

inst-logo.png

inst-logo.png

91 ms

gplus-logo.png

gplus-logo.png

90 ms

y-logo.png

y-logo.png

90 ms

ta-logo.png

ta-logo.png

92 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCGPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCGPrQ.ttf

96 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCGPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCGPrQ.ttf

104 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCGPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCGPrQ.ttf

124 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtaorCGPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtaorCGPrQ.ttf

114 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvao7CGPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvao7CGPrQ.ttf

112 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpbCGPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpbCGPrQ.ttf

113 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCGPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCGPrQ.ttf

112 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtapbCGPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtapbCGPrQ.ttf

110 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtzpbCGPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtzpbCGPrQ.ttf

124 ms

modules.woff

modules.woff

112 ms

widget_app_base_1724849559553.js

widget_app_base_1724849559553.js

17 ms

Accessibility Review

portworks.com accessibility score

89

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

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

portworks.com best practices score

67

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

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

Page has valid source maps

SEO Factors

portworks.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 Portworks.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 Portworks.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

portworks.com

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