3.8 sec in total
572 ms
2.8 sec
433 ms
Welcome to amphora.jp homepage info - get ready to check Amphora best content right away, or after learning these important things about amphora.jp
アンフォラ オリエンタルジュエリー・セレクトショップ
Visit amphora.jpWe analyzed Amphora.jp page load time and found that the first response time was 572 ms and then it took 3.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
amphora.jp performance score
name
value
score
weighting
Value5.5 s
6/100
10%
Value30.4 s
0/100
25%
Value13.0 s
2/100
10%
Value100 ms
98/100
30%
Value0.541
14/100
15%
Value16.6 s
5/100
10%
572 ms
177 ms
317 ms
35 ms
71 ms
Our browser made a total of 71 requests to load all elements on the main page. We found that 77% of them (55 requests) were addressed to the original Amphora.jp, 8% (6 requests) were made to Trustlogo.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Amphora.jp.
Page size can be reduced by 106.5 kB (11%)
990.3 kB
883.8 kB
In fact, the total size of Amphora.jp main page is 990.3 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. 25% of websites need less resources to load. Images take 896.9 kB which makes up the majority of the site volume.
Potential reduce by 32.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. This page needs HTML code to be minified as it can gain 4.1 kB, which is 11% 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 32.3 kB or 82% of the original size.
Potential reduce by 38.1 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. Amphora images are well optimized though.
Potential reduce by 25.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 25.1 kB or 61% of the original size.
Potential reduce by 11.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. Amphora.jp needs all CSS files to be minified and compressed as it can save up to 11.1 kB or 85% of the original size.
Number of requests can be reduced by 9 (13%)
67
58
The browser has sent 67 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Amphora. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 5 to 1 for JavaScripts and as a result speed up the page load time.
amphora.jp
572 ms
flash_activate.js
177 ms
stylesheet.css
317 ms
trustlogo.js
35 ms
trustlogo.js
71 ms
urchin.js
5 ms
trustlogo.js
47 ms
125_b.GIF
527 ms
turkish125.GIF
471 ms
img218.gif
620 ms
580vintage.JPG
1252 ms
pixel_trans.gif
172 ms
logo.GIF
292 ms
mypage.gif
325 ms
cart.gif
340 ms
button_quick_find.gif
347 ms
menutxt.GIF
363 ms
164wrapping.JPG
539 ms
itemstxt.GIF
452 ms
product_thumb.php
553 ms
infotxt.GIF
509 ms
276ayala.JPG
854 ms
276vintage.JPG
1084 ms
276coeuldelion.JPG
775 ms
276mariana.JPG
1010 ms
catEASTER.JPG
901 ms
276romanglass.JPG
882 ms
276egyptian.JPG
1130 ms
276beypazar.JPG
1362 ms
catTURKOISE.JPG
1049 ms
catPRECIOUS.JPG
1088 ms
catNOMAD.JPG
1185 ms
catTurkistan.JPG
1211 ms
276nazarboncug.JPG
1265 ms
276igneoya.JPG
1273 ms
276alsameiya.JPG
1298 ms
276ottoman.JPG
1354 ms
product_thumb.php
1435 ms
button_buy_now.gif
1444 ms
product_thumb.php
1522 ms
product_thumb.php
1520 ms
product_thumb.php
1585 ms
product_thumb.php
1588 ms
product_thumb.php
1666 ms
product_thumb.php
1690 ms
580coeurdelion2012.JPG
1310 ms
580kupeler.JPG
991 ms
product_thumb.php
1745 ms
like.php
123 ms
banner.gif
562 ms
276wrapping.JPG
508 ms
logo.GIF
346 ms
stylesheet.css
1539 ms
seal_bg.gif
14 ms
navi_bg.GIF
1578 ms
secure_site.GIF
392 ms
warranty_level.gif
20 ms
__utm.gif
11 ms
seal_bg.gif
10 ms
qeKvIRsJabD.js
298 ms
LVx-xkvaJ0b.png
338 ms
warranty_level.gif
8 ms
titlebar.gif
1473 ms
support.JPG
1525 ms
card.GIF
1539 ms
ginko.GIF
1546 ms
sagawa.GIF
1550 ms
telefon.JPG
1477 ms
ourshops.JPG
1430 ms
bijoux.GIF
1482 ms
uuda.JPG
1512 ms
amphora.jp accessibility score
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
[aria-hidden="true"] elements contain focusable descendents
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.
Definition list items are not wrapped in <dl> elements
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
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
Image elements do not have [alt] attributes
Links do not have a discernible name
amphora.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
amphora.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
robots.txt is not valid
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
Document uses legible font sizes
JA
JA
EUC-JP
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Amphora.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it matches the claimed language. Our system also found out that Amphora.jp main page’s claimed encoding is euc-jp. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
amphora.jp
Open Graph description is not detected on the main page of Amphora. 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: