Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the conditional-extra-fees-woocommerce domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6121

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the ultimate-member domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6121

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the follow_up_emails domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6121

Deprecated: Creation of dynamic property Foxpost_Wc_Shipping_Logger::$logger is deprecated in /var/www/html/wp-content/plugins/foxpost-wc-shipping/includes/class-foxpost-wc-shipping-logger.php on line 39

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the uncanny-automator-pro domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6121

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the woocommerce domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6121

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pay-via-barion-for-woocommerce domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6121

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the uncanny-automator domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6121

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the woocommerce-jos-autocoupon domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6121

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the viwec-email-template-customizer domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6121

Deprecated: Creation of dynamic property FUE_Addon_Woocommerce::$wc_conditions is deprecated in /var/www/html/wp-content/plugins/woocommerce-follow-up-emails/includes/addons/class-fue-addon-woocommerce.php on line 70

Deprecated: Creation of dynamic property FUE_Addon_Twitter_Tweeter::$fue_twitter is deprecated in /var/www/html/wp-content/plugins/woocommerce-follow-up-emails/includes/addons/twitter/class-fue-addon-twitter-tweeter.php on line 15

Deprecated: Creation of dynamic property FUE_Addon_Twitter::$twitter_tweet is deprecated in /var/www/html/wp-content/plugins/woocommerce-follow-up-emails/includes/addons/class-fue-addon-twitter.php on line 41

Deprecated: Creation of dynamic property FUE_Addon_Twitter::$twitter_frontend is deprecated in /var/www/html/wp-content/plugins/woocommerce-follow-up-emails/includes/addons/class-fue-addon-twitter.php on line 42

Deprecated: Creation of dynamic property FUE_Addon_Twitter::$twitter_scheduler is deprecated in /var/www/html/wp-content/plugins/woocommerce-follow-up-emails/includes/addons/class-fue-addon-twitter.php on line 43

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the woo-cart-abandonment-recovery domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6121
Mikor jó a szemüvegkeret mérete? | Eyewear Store

.wp-grid-builder .wpgb-card.wpgb-card-hidden .wpgb-card-wrapper{opacity:1!important;visibility:visible!important;transform:none!important}.wpgb-facet {opacity:1!important;pointer-events:auto!important}.wpgb-facet *:not(.wpgb-pagination-facet){display:none}

Mikor jó a szemüvegkeret mérete?

A szemüvegkereteknek nincsen sablon méretezése, mint a ruházati cikkeknek. Ezért fontos tudni, milyen szempontok alapján tudjuk eldönteni, hogy megfelelő-e a mérete vagy sem.

A szemüvegkeretek méretei

Általában a szemüvegkeretek szárában feltüntetnek méreteket ebben a sorrendben: lencseszélesség, híd, szárhossz.

A szemüvegek méretezésénél általában a lencse szélesség a mérvadó. Bár lehetnek átfedések, de nagyjából így lehet csoportosítani:

Bébi méret: 34-40 mm
Gyerek: 42-48 mm
Tini: 48-52 mm
Felnőtt: 50-től felfelé
Női átlag: kb. 54
Férfi átlag: kb. 56

A saját kereted méreteit egy vonalzó segítségével könnyedén letudod mérni. Ehhez lehet viszonyítani új szemüveg választásánál.

Mikor jó a szélesség?

Mikor nem jó?

Akkor kicsi, ha a szárai kifelé állnak. Akkor nagy, ha túl nagy hely van a halánték és a szár között.

Tehát akkor lesz tökéletes a méret, ha a szárai szép egyenesen, párhuzamosan haladnak a fül mögé.

Mikor jó a híd?

Sok viselőnél problémát okoz, hogy az átlagnál szélesebb vagy szűkebb orrnyerge van. Ilyen esetekben a híd szélességére is figyelni kell.

Ha túl széles az orrnyergünk, akkor átlag méretnél rés keletkezhet középen és a keret túl magasan ül.

Ha túl szűk az orrnyergünk, akkor pedig nem lesz elég stabil, vagy hozzáérhet az arcunkhoz a keret rész.

Tehát akkor tökéletes egy szemüveg, ha az orrnyergünket szépen körbeöleli, a szárai szép párhuzamosan futnak és lehetőség szerint a lencse felső 1/2 részén nézünk keresztül.

Gyakori problémák és megoldások

Amennyiben nem tökéletes a keretválasztás vagy rossz a beállítása, okozhat egészen kellemetlen panaszokat is. Például ha csúszkál az orrunkon az nem fog fájni, de ki szeretné állandóan felfelé tologatni? Ha túl szorosra sikerül akkor pedig feltöri a füledet vagy az orrodat, ez tényleg kellemetlen.

Alábbi két blog cikkünkben kitértünk részletesebben ezeknek a problémáknak a megoldására: